Add SARIF export support#113
Open
jadenfix wants to merge 3 commits into
Open
Conversation
|
@jadenfix is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
jadenfix
force-pushed
the
jaden/sarif-export
branch
from
July 19, 2026 21:07
a3bfbdf to
3f987d6
Compare
jadenfix
marked this pull request as ready for review
July 19, 2026 21:10
Author
|
Ready for review at |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds
deepsec export --format sarif --out <file>with SARIF 2.1.0 rules, repository-relative source locations, DeepSec metadata, and deterministic partial fingerprints. GitHub code scanning receives security severity for security findings and correctness metadata for non-security bugs. Sparse evidence lines are emitted as one exact primary location plus related locations.SARIF now requires exactly one project per file so repository-relative paths cannot be attributed to the wrong repository. The official GitHub upload action and required workflow permission are documented.
Why
JSON and Markdown exports require custom integrations. SARIF gives DeepSec users a standard interchange format for code-scanning consumers such as GitHub while preserving correct alert classification and stable identity.
Verification
pnpm lint,pnpm knip,pnpm -r build,pnpm bundle, andpnpm typecheck:deepsecpassNotes for reviewer
DeepSec emits a stable generic partial fingerprint. The official GitHub upload action augments uploaded results with its source-based
primaryLocationLineHash. The branch is based on the currentmain.