Home/SciEvalKit/Trust report

Trust and health report

SciEvalKit - trust report

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

GraphCanon updated Oct 18, 2026 · GitHub synced Oct 18, 2026

Maintenance

Snapshot computed Oct 18, 2026

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

Steady60% signal

last push 49d before snapshot

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

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 1108941331
  • Not a fork
  • GitHub organization account
  • Computed Oct 18, 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; additional observations pending review
Last query
Jul 15, 2026
Scanner
osv@v1
Published findings
1
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)

PYSEC-2023-183
opencv-python@4.7.0.72 · 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/internscience-scievalkit/trust.

Common questions

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