Trust and health report
HRM - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 4d · GitHub synced 4d
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
last push 138d ago
+17 stars (30d) · 0 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 1016423859
- Not a fork
- Verified publisher: organization account
- Computed 4d
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-11- Last query
- 1mo
- 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/sapientinc-hrm/trust.
Common questions
- Is HRM maintained?
- GraphCanon rates HRM "Slowing" (36% maintenance signal from public GitHub metadata, computed 4d). Last push was 138 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is HRM safe to use?
- Last scanned 1mo (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 HRM as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is HRM a fork?
- No. HRM is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does HRM have known security vulnerabilities?
- Last scanned 1mo (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 HRM trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 4d (methodology github_public_v1).
- What does GraphCanon never claim about HRM?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for HRM. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for HRM?
- 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.