Skip to content

ci: add ThreatCrush security scan - #17

Merged
ralyodio merged 1 commit into
masterfrom
chore/threatcrush-scan
Aug 3, 2026
Merged

ci: add ThreatCrush security scan#17
ralyodio merged 1 commit into
masterfrom
chore/threatcrush-scan

Conversation

@ralyodio

@ralyodio ralyodio commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Installs threatcrush-scan@1.1.0 from the sh1pt Actions Store.

Scans pull requests for hardcoded credentials, injection, SSRF, unsafe deserialisation, XXE and dependency tampering. Findings go to the Security tab as SARIF and to a PR comment; snippets are redacted, so no credential material reaches a CI log.

Report-only. It will not fail a pull request. Once the existing findings are triaged, set the pack's failOn input to critical,high.

Coverage against profullstack/malware-test-prs: 90.32% true-positive rate at a 0.0% false-positive rate against its control group of correct implementations.

Generated by the fleet renderer — the managed header hash matches the pack source.

🤖 Generated with Claude Code

Installs threatcrush-scan@1.1.0 from the sh1pt Actions Store.
Scans pull requests for hardcoded credentials, injection, SSRF, unsafe
deserialisation and dependency tampering; uploads SARIF to the Security
tab.

Report-only — it will not fail a pull request. Set the pack's failOn
input to critical,high once the existing findings are triaged.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown

ThreatCrush Security Scan

0 finding(s)

No findings.

@ralyodio
ralyodio marked this pull request as ready for review August 3, 2026 14:21
@ralyodio
ralyodio merged commit a354c7e into master Aug 3, 2026
10 checks passed
@ralyodio
ralyodio deleted the chore/threatcrush-scan branch August 3, 2026 14:21
ralyodio added a commit that referenced this pull request Aug 13, 2026
No Rust changed since v0.2.25. Every commit in this range is web, CI or docs,
so the binaries this tag builds are identical to the previous ones and the
version marks the site rather than the client:

  - blog: serve last known good instead of 500 when SQLite Cloud blinks (#18)
  - ci: add ThreatCrush security scan (#17)
  - feat(web): WebMCP callout on the homepage (#16)
  - docs(web): document WebMCP tools (#15)
  - feat(web): WebMCP support on c0mpute.com (#14)

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants