Trust and health report
filco - 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.
Dormant18% signal
last push 846d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 718814616
- 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
- 46
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
transformers has a Deserialization of Untrusted Data vulnerability
transformers@4.25.1 · CVE-2023-6730 · osv@v1
requirements.txt
HuggingFace transformers vulnerable to remote code execution
transformers@4.25.1 · CVE-2026-4372 · osv@v1
requirements.txt
Deserialization of Untrusted Data in Hugging Face Transformers
transformers@4.25.1 · CVE-2024-11394 · osv@v1
requirements.txt
Deserialization of Untrusted Data in Hugging Face Transformers
transformers@4.25.1 · CVE-2024-11392 · osv@v1
requirements.txt
transformers has a Deserialization of Untrusted Data vulnerability
transformers@4.25.1 · CVE-2023-7018 · osv@v1
requirements.txt
Deserialization of Untrusted Data in Hugging Face Transformers
transformers@4.25.1 · CVE-2024-11393 · osv@v1
requirements.txt
transformers has Insecure Temporary File
transformers@4.25.1 · CVE-2023-2800 · osv@v1
requirements.txt
Transformers is vulnerable to ReDoS attack through its DonutProcessor class
transformers@4.25.1 · CVE-2025-3933 · osv@v1
requirements.txt
Hugging Face Transformers vulnerable to Regular Expression Denial of Service (ReDoS) in the AdamWeightDecay optimizer
transformers@4.25.1 · CVE-2025-6921 · osv@v1
requirements.txt
Hugging Face Transformers is vulnerable to ReDoS through its MarianTokenizer
transformers@4.25.1 · CVE-2025-6638 · osv@v1
requirements.txt
HuggingFace Transformers allows for arbitrary code execution in the `Trainer` class
transformers@4.25.1 · CVE-2026-1839 · osv@v1
requirements.txt
Transformers Regular Expression Denial of Service (ReDoS) vulnerability
transformers@4.25.1 · CVE-2024-12720 · osv@v1
requirements.txt
Hugging Face Transformers Regular Expression Denial of Service (ReDoS) vulnerability
transformers@4.25.1 · CVE-2025-5197 · osv@v1
requirements.txt
Transformers Regular Expression Denial of Service (ReDoS) vulnerability
transformers@4.25.1 · CVE-2025-1194 · osv@v1
requirements.txt
Transformers vulnerable to ReDoS attack through its get_imports() function
transformers@4.25.1 · CVE-2025-3264 · osv@v1
requirements.txt
Transformers's ReDoS vulnerability in get_configuration_file can lead to catastrophic backtracking
transformers@4.25.1 · CVE-2025-3263 · osv@v1
requirements.txt
Hugging Face Transformers Regular Expression Denial of Service
transformers@4.25.1 · CVE-2025-2099 · osv@v1
requirements.txt
Hugging Face Transformers library has Regular Expression Denial of Service
transformers@4.25.1 · CVE-2025-6051 · osv@v1
requirements.txt
Transformers Deserialization of Untrusted Data vulnerability
transformers@4.25.1 · CVE-2024-3568 · osv@v1
requirements.txt
Transformers's Improper Input Validation vulnerability can be exploited through username injection
transformers@4.25.1 · CVE-2025-3777 · osv@v1
requirements.txt
PYSEC-2025-211
transformers@4.25.1 · CVE-2025-14920 · osv@v1
requirements.txt
PYSEC-2025-212
transformers@4.25.1 · CVE-2025-14921 · osv@v1
requirements.txt
PYSEC-2025-213
transformers@4.25.1 · CVE-2025-14924 · osv@v1
requirements.txt
PYSEC-2025-214
transformers@4.25.1 · CVE-2025-14926 · osv@v1
requirements.txt
PYSEC-2025-215
transformers@4.25.1 · CVE-2025-14927 · osv@v1
requirements.txt
PYSEC-2025-216
transformers@4.25.1 · CVE-2025-14928 · osv@v1
requirements.txt
PYSEC-2025-217
transformers@4.25.1 · CVE-2025-14929 · osv@v1
requirements.txt
PYSEC-2025-218
transformers@4.25.1 · CVE-2025-14930 · 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/zorazrw-filco/trust.
Common questions
- Is filco maintained?
- GraphCanon rates filco "Dormant" (18% maintenance signal from public GitHub metadata, computed 3w). Last push was 846 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is filco safe to use?
- Last scanned 1mo (deps profile). Status: 1 critical, 5 high, 12 medium, 28 low - 1 critical, 5 high, 12 medium, 28 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 filco as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is filco a fork?
- No. filco is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does filco have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 1 critical, 5 high, 12 medium, 28 low - 1 critical, 5 high, 12 medium, 28 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 filco 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 filco?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for filco. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for filco?
- 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.