Trust and health report
ATLAS_OS - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated today · GitHub synced today
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
last push 61d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 1224062178
- Not a fork
- Personal account
- Computed today
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 published findings from this source as of 2026-07-15- Last query
- today
- Scanner
- osv@v1
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceMethod 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/lucapohl-angel-atlas-os/trust.
Common questions
- Is ATLAS_OS maintained?
- GraphCanon rates ATLAS_OS "Steady" (60% maintenance signal from public GitHub metadata, computed today). Last push was 61 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is ATLAS_OS safe to use?
- Last scanned today (deps profile). Status: No criticals. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits. GraphCanon does not certify ATLAS_OS as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is ATLAS_OS a fork?
- No. ATLAS_OS is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does ATLAS_OS have known security vulnerabilities?
- Last scanned today (deps profile). Status: No criticals. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits.
- How often is the ATLAS_OS trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).
- What does GraphCanon never claim about ATLAS_OS?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for ATLAS_OS. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for ATLAS_OS?
- 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.