Trust and health report
awesome - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 2w · GitHub synced 2w
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Steady60% signal
last push 34d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 21737465
- Not a fork
- Personal account
- Computed 2w
Security intelligence
Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.
OSV dependency advisories
No lockfile (source not queried)- Last query
- 1mo
- Scanner
- osv@v1
OpenSSF Scorecard
Published findings- Last query
- 1w
- Scanner
- openssf-scorecard@v1
- Stored findings
- 11
Weekly public scans omit some checks at scale.
View source evidenceOpenSSF Scorecard checks
Maintained (4/10): 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#maintainedPinned-Dependencies (0/10): dependency not pinned by hash detected -- score normalized to 0
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#pinned-dependenciesCode-Review (6/10): Found 20/30 approved changesets -- score normalized to 6
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#code-reviewPackaging (-1/10): packaging workflow not detected
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#packagingToken-Permissions (0/10): detected GitHub workflow tokens with excessive permissions
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#token-permissionsCII-Best-Practices (0/10): no effort to earn an OpenSSF best practices badge detected
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#cii-best-practicesFuzzing (0/10): project is not fuzzed
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#fuzzingSigned-Releases (-1/10): no releases found
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#signed-releasesSecurity-Policy (0/10): security policy file not detected
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#security-policyBranch-Protection (0/10): branch protection not enabled on development/release branches
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#branch-protectionSAST (0/10): SAST tool is not run on all commits -- score normalized to 0
https://github.com/ossf/scorecard/blob/40c1e35996730d4fdcbdb2e6a23917a2467e29b7/docs/checks.md#sastMethod and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/sindresorhus-awesome/trust.
Common questions
- Is awesome maintained?
- GraphCanon rates awesome "Steady" (60% maintenance signal from public GitHub metadata, computed 2w). Last push was 34 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is awesome safe to use?
- Last scanned 1mo (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits. GraphCanon does not certify awesome as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is awesome a fork?
- No. awesome is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does awesome have known security vulnerabilities?
- Last scanned 1mo (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits.
- How often is the awesome trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).
- What does GraphCanon never claim about awesome?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for awesome. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for awesome?
- Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.