Trust and health report
AgentsMesh - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated 3w · GitHub synced 3w
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Very active96% signal
last push 1d ago · last release 3w · 30 releases (90d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 1169101061
- Not a fork
- Verified publisher: organization account
- Computed 3w
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
- 24
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-pjcq-xvwq-hhpj
github.com/Azure/go-ntlmssp@v0.0.0-20221128193559-754e69321358 · osv@v1
go.sum
GHSA-xmrv-pmrh-hhx2
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream@v1.7.4 · osv@v1
go.sum
GO-2026-5764
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream@v1.7.4 · osv@v1
go.sum
GHSA-pxq6-2prw-chj9
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GHSA-rg2x-37c3-w2rh
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GHSA-vp62-88p7-qqf5
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GHSA-x744-4wpc-v9h2
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GHSA-x86f-5xw2-fm2r
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GO-2026-4883
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GO-2026-4887
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GO-2026-5617
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GO-2026-5668
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GO-2026-5746
github.com/docker/docker@v28.3.3+incompatible · osv@v1
go.sum
GHSA-qqx8-2xmm-jrv8
github.com/go-acme/lego/v4@v4.33.0 · osv@v1
go.sum
GHSA-9jj7-4m8r-rfcm
github.com/jackc/pgx/v5@v5.6.0 · osv@v1
go.sum
GHSA-j88v-2chj-qfwx
github.com/jackc/pgx/v5@v5.6.0 · osv@v1
go.sum
GHSA-xgrm-4fwx-7qm8
github.com/jackc/pgx/v5@v5.6.0 · osv@v1
go.sum
GO-2026-4771
github.com/jackc/pgx/v5@v5.6.0 · osv@v1
go.sum
GO-2026-4772
github.com/jackc/pgx/v5@v5.6.0 · osv@v1
go.sum
GO-2026-5004
github.com/jackc/pgx/v5@v5.6.0 · osv@v1
go.sum
GHSA-vvgj-x9jq-8cj9
github.com/quic-go/quic-go@v0.59.0 · osv@v1
go.sum
GO-2026-5676
github.com/quic-go/quic-go@v0.59.0 · osv@v1
go.sum
GHSA-479m-364c-43vc
github.com/russellhaering/goxmldsig@v1.4.0 · osv@v1
go.sum
GO-2026-4753
github.com/russellhaering/goxmldsig@v1.4.0 · osv@v1
go.sum
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/agentsmesh-agentsmesh/trust.
Common questions
- Is AgentsMesh maintained?
- GraphCanon rates AgentsMesh "Very active" (96% maintenance signal from public GitHub metadata, computed 3w). Last push was 1 days ago. 30 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is AgentsMesh safe to use?
- Last scanned 1mo (deps profile). Status: 24 low - 24 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 AgentsMesh as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is AgentsMesh a fork?
- No. AgentsMesh is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does AgentsMesh have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 24 low - 24 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 AgentsMesh trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 3w (methodology github_public_v1).
- What does GraphCanon never claim about AgentsMesh?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for AgentsMesh. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for AgentsMesh?
- 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.