Trust and health report
ai-getting-started - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 1w · GitHub synced 1w
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Dormant18% signal
last push 723d ago
0 stars (30d) · 0 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 654359433
- Not a fork
- Verified publisher: organization account
- Computed 1w
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
Published findings- Last query
- 1mo
- Scanner
- osv@v1
- Stored findings
- 31
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-968p-4wvh-cqc8
@babel/runtime@7.24.7 · osv@v1
package-lock.json
GHSA-vqx2-fgx2-5wq9
@clerk/nextjs@5.1.4 · osv@v1
package-lock.json
GHSA-2g4f-4pwh-qvx6
ajv@6.12.6 · osv@v1
package-lock.json
GHSA-8r88-6cj9-9fh5
@supabase/auth-js@2.64.2 · osv@v1
package-lock.json
GHSA-f886-m6hf-6m8v
brace-expansion@2.0.1 · osv@v1
package-lock.json
GHSA-v6h2-p8h4-qcjw
brace-expansion@2.0.1 · osv@v1
package-lock.json
GHSA-23c5-xmqv-rm74
minimatch@9.0.3 · osv@v1
package-lock.json
GHSA-3ppc-4f35-3m26
minimatch@9.0.3 · osv@v1
package-lock.json
GHSA-7r86-cg39-jmmj
minimatch@9.0.3 · osv@v1
package-lock.json
GHSA-rwvc-j5jr-mgvh
ai@2.2.37 · osv@v1
package-lock.json
GHSA-3g43-6gmg-66jw
axios@0.26.1 · osv@v1
package-lock.json
GHSA-3p68-rc4w-qgx5
axios@0.26.1 · osv@v1
package-lock.json
GHSA-43fc-jf86-j433
axios@0.26.1 · osv@v1
package-lock.json
GHSA-5c9x-8gcm-mpgx
axios@0.26.1 · osv@v1
package-lock.json
GHSA-62hf-57xw-28j9
axios@0.26.1 · osv@v1
package-lock.json
GHSA-6chq-wfr3-2hj9
axios@0.26.1 · osv@v1
package-lock.json
GHSA-898c-q2cr-xwhg
axios@0.26.1 · osv@v1
package-lock.json
GHSA-fvcv-3m26-pcqx
axios@0.26.1 · osv@v1
package-lock.json
GHSA-hfxv-24rg-xrqf
axios@0.26.1 · osv@v1
package-lock.json
GHSA-j5f8-grm9-p9fc
axios@0.26.1 · osv@v1
package-lock.json
GHSA-jr5f-v2jv-69x6
axios@0.26.1 · osv@v1
package-lock.json
GHSA-m7pr-hjqh-92cm
axios@0.26.1 · osv@v1
package-lock.json
GHSA-p92q-9vqr-4j8v
axios@0.26.1 · osv@v1
package-lock.json
GHSA-pf86-5x62-jrwf
axios@0.26.1 · osv@v1
package-lock.json
GHSA-pjwm-pj3p-43mv
axios@0.26.1 · osv@v1
package-lock.json
GHSA-pmwg-cvhr-8vh7
axios@0.26.1 · osv@v1
package-lock.json
GHSA-vf2m-468p-8v99
axios@0.26.1 · osv@v1
package-lock.json
GHSA-w9j2-pvgh-6h63
axios@0.26.1 · osv@v1
package-lock.json
GHSA-wf5p-g6vw-rhxx
axios@0.26.1 · osv@v1
package-lock.json
GHSA-xhjh-pmcv-23jw
axios@0.26.1 · osv@v1
package-lock.json
GHSA-xx6v-rp6x-q39c
axios@0.26.1 · osv@v1
package-lock.json
Method 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/a16z-infra-ai-getting-started/trust.
Common questions
- Is ai-getting-started maintained?
- GraphCanon rates ai-getting-started "Dormant" (18% maintenance signal from public GitHub metadata, computed 1w). Last push was 723 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is ai-getting-started safe to use?
- Last scanned 1mo (deps profile). Status: 31 low - 31 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify ai-getting-started as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is ai-getting-started a fork?
- No. ai-getting-started is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does ai-getting-started have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 31 low - 31 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
- How often is the ai-getting-started trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 1w (methodology github_public_v1).
- What does GraphCanon never claim about ai-getting-started?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for ai-getting-started. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for ai-getting-started?
- 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.