Trust and health report
stt - 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 · 29 views this month
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Slowing36% signal
last push 189d ago · last release 1y
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 736697367
- Not a fork
- Personal 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
- 27
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
PyTorch: `torch.load` with `weights_only=True` leads to remote code execution
torch@2.1.2 · CVE-2025-32434 · osv@v1
requirements.txt
PyTorch heap buffer overflow vulnerability
torch@2.1.2 · CVE-2024-31580 · osv@v1
requirements.txt
Pytorch use-after-free vulnerability
torch@2.1.2 · CVE-2024-31583 · osv@v1
requirements.txt
PyTorch Improper Resource Shutdown or Release vulnerability
torch@2.1.2 · CVE-2025-3730 · osv@v1
requirements.txt
PyTorch is Vulnerable to Memory Consumption through pad_packed_sequence Function
torch@2.1.2 · CVE-2025-2998 · osv@v1
requirements.txt
PyTorch is vulnerable to memory corruption through its unpack_sequence function
torch@2.1.2 · CVE-2025-2999 · osv@v1
requirements.txt
PyTorch susceptible to local Denial of Service
torch@2.1.2 · CVE-2025-2953 · osv@v1
requirements.txt
PyTorch Tuple Handler is Vulnerable to Memory Corruption through Manipulation of None Argument
torch@2.1.2 · CVE-2025-2148 · osv@v1
requirements.txt
PyTorch is vulnerable to memory corruption through its torch.lstm_cell function
torch@2.1.2 · CVE-2025-3001 · osv@v1
requirements.txt
PyTorch is vulnerable to memory corruption through its torch.jit.script function
torch@2.1.2 · CVE-2025-3000 · osv@v1
requirements.txt
PyTorch: Manipulation of the argument scale/zero_point leads to improper initialization via Quantized Sigmoid Module
torch@2.1.2 · CVE-2025-2149 · osv@v1
requirements.txt
PYSEC-2024-250
torch@2.1.2 · CVE-2024-31584 · osv@v1
requirements.txt
PYSEC-2024-259
torch@2.1.2 · CVE-2024-48063 · osv@v1
requirements.txt
PYSEC-2025-198
torch@2.1.2 · CVE-2025-46148 · osv@v1
requirements.txt
PYSEC-2025-203
torch@2.1.2 · CVE-2025-55551 · osv@v1
requirements.txt
PYSEC-2025-204
torch@2.1.2 · CVE-2025-55552 · osv@v1
requirements.txt
PYSEC-2025-205
torch@2.1.2 · CVE-2025-55553 · osv@v1
requirements.txt
PYSEC-2025-206
torch@2.1.2 · CVE-2025-55554 · osv@v1
requirements.txt
PYSEC-2025-207
torch@2.1.2 · CVE-2025-55557 · osv@v1
requirements.txt
PYSEC-2025-208
torch@2.1.2 · CVE-2025-55558 · osv@v1
requirements.txt
PYSEC-2025-209
torch@2.1.2 · CVE-2025-55560 · osv@v1
requirements.txt
PYSEC-2026-139
torch@2.1.2 · CVE-2026-4538 · 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/jianchang512-stt/trust.
Common questions
- Is stt maintained?
- GraphCanon rates stt "Slowing" (36% maintenance signal from public GitHub metadata, computed 3w). Last push was 189 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is stt safe to use?
- Last scanned 1mo (deps profile). Status: 1 critical, 2 high, 3 medium, 21 low - 1 critical, 2 high, 3 medium, 21 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 stt as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is stt a fork?
- No. stt is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does stt have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 1 critical, 2 high, 3 medium, 21 low - 1 critical, 2 high, 3 medium, 21 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 stt 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 stt?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for stt. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for stt?
- 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.