Home/autoMate/Trust report

Trust and health report

autoMate - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated Sep 20, 2026 · GitHub synced Sep 20, 2026

Maintenance

Snapshot computed Sep 20, 2026

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Very active96% signal

last push 2d before snapshot · last release Apr 28, 2026

+20 stars (30d) · +1 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 745749489
  • Not a fork
  • Personal account
  • Computed Sep 20, 2026

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
Jul 15, 2026
Scanner
osv@v1
Published findings
20
View source evidence

deps.dev advisories

Not queried
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Not queried
Scanner
openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-mr82-8j83-vxmv
pydantic@2.0 · osv@v1
requirements.txt
PYSEC-2026-1812
pydantic@2.0 · osv@v1
requirements.txt
GHSA-3ww4-gg4f-jr7f
cryptography@41.0 · osv@v1
requirements.txt
GHSA-537c-gmf6-5ccf
cryptography@41.0 · osv@v1
requirements.txt
GHSA-6vqw-3v5j-54x4
cryptography@41.0 · osv@v1
requirements.txt
GHSA-9v9h-cgj8-h64p
cryptography@41.0 · osv@v1
requirements.txt
GHSA-cf7p-gm2m-833m
cryptography@41.0 · osv@v1
requirements.txt
GHSA-h4gh-qq45-vh27
cryptography@41.0 · osv@v1
requirements.txt
GHSA-jfhm-5ghh-2f97
cryptography@41.0 · osv@v1
requirements.txt
GHSA-jm77-qphf-c4w8
cryptography@41.0 · osv@v1
requirements.txt
GHSA-m959-cc7f-wv43
cryptography@41.0 · osv@v1
requirements.txt
GHSA-r6ph-v2qm-q3c2
cryptography@41.0 · osv@v1
requirements.txt
GHSA-v8gr-m533-ghj9
cryptography@41.0 · osv@v1
requirements.txt
PYSEC-2023-112
cryptography@41.0 · osv@v1
requirements.txt
PYSEC-2023-254
cryptography@41.0 · osv@v1
requirements.txt
PYSEC-2024-225
cryptography@41.0 · osv@v1
requirements.txt
PYSEC-2026-1283
cryptography@41.0 · osv@v1
requirements.txt
PYSEC-2026-1285
cryptography@41.0 · osv@v1
requirements.txt
PYSEC-2026-2141
cryptography@41.0 · osv@v1
requirements.txt
PYSEC-2026-35
cryptography@41.0 · osv@v1
requirements.txt

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/yuruotong1-automate/trust.

Common questions

Is autoMate maintained?
GraphCanon rates autoMate "Very active" (96% maintenance signal from public GitHub metadata, computed Sep 20, 2026). At that snapshot, the last push was 2 days earlier. This is a recency heuristic, not a guarantee the project will stay maintained.
Is autoMate safe to use?
Last scanned Jul 15, 2026 (deps profile). Published findings: 20 low. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify autoMate as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is autoMate a fork?
No. autoMate is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does autoMate have known security vulnerabilities?
Last scanned Jul 15, 2026 (deps profile). Published findings: 20 low. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
How often is the autoMate trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 20, 2026 (methodology github_public_v1).
What does GraphCanon never claim about autoMate?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for autoMate. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for autoMate?
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.

Was this helpful?

Anonymous feedback helps us improve pages and translations.