Home/EasyEdit/Trust report

Trust and health report

EasyEdit - trust report

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

GraphCanon updated 2w · GitHub synced 2w · 26 views this month

Maintenance

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

Active82% signal

last push 24d ago

Provenance

Repository identity and fork provenance (github_public_v1).

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
25
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-qfhq-4f3w-5fph
torch@2.9.1 · osv@v1
requirements.txt
GHSA-rrmf-rvhw-rf47
torch@2.9.1 · osv@v1
requirements.txt
PYSEC-2026-139
torch@2.9.1 · osv@v1
requirements.txt
GHSA-469j-vmhf-r6v7
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-68j8-pq59-fqgm
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-7p94-766c-hgjp
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-cgvx-9447-vcch
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-f8m6-h2c7-8h9x
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-gfwx-w7gr-fvh7
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-h8wq-7xc4-p3qx
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-jm6w-m3j8-898g
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-p4gq-832x-fm9v
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-rf74-v2fm-23pw
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-rqjh-jp2r-59cj
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2022-5
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2024-167
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2026-2078
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2026-2085
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2026-597
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2026-96
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2026-97
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2026-98
nltk@3.6.5 · osv@v1
requirements.txt
PYSEC-2026-99
nltk@3.6.5 · osv@v1
requirements.txt
GHSA-38vq-g6vr-w8wf
sentencepiece@0.2.0 · osv@v1
requirements.txt
PYSEC-2026-1909
sentencepiece@0.2.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/zjunlp-easyedit/trust.

Common questions

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