---
title: "autoMate trust report"
type: "trust-report"
slug: "yuruotong1-automate"
canonical_url: "https://www.graphcanon.com/tools/yuruotong1-automate/trust"
computed_at: "2026-07-15T11:16:49.624Z"
maintenance_label: "Steady"
security_status: "findings"
---

# autoMate trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and external security intelligence providers. Not a security guarantee._

## Maintenance

- Label: Steady (60% recency signal)
- Days since last push: 76
- Last release: 2026-04-28T07:58:17Z
- Releases (90d): 27
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 745749489
- Not a fork
- Owner type: User
- Computed at: 2026-07-15T11:16:49.624Z
- Methodology: github_public_v1

## Security intelligence

- **OSV dependency advisories**: Published findings
  - Last query: 2026-07-15T11:16:51.487837+00:00
  - Evidence: https://osv.dev/
- **deps.dev advisories**: Not queried
  - Evidence: https://deps.dev/
- **OpenSSF Scorecard**: Not queried
  - Evidence: https://api.securityscorecards.dev/projects/github.com/yuruotong1/autoMate
  - Note: Weekly public scans omit some checks at scale.

### Findings

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

## Method and caveats

These are heuristics from public GitHub data and external security intelligence providers, sourced and dated. 
"No published findings from this source" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is autoMate maintained?

GraphCanon rates autoMate "Steady" (60% maintenance signal from public GitHub metadata, computed today). Last push was 76 days ago. 27 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is autoMate safe to use?

Last scanned today (deps profile). Status: 20 low - 20 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 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 today (deps profile). Status: 20 low - 20 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 autoMate 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 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](/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](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/yuruotong1-automate/trust`](/api/graphcanon/tools/yuruotong1-automate/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_