Home/ollama-js/Trust report

Trust and health report

ollama-js - trust report

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

GraphCanon updated Sep 20, 2026 · GitHub synced Sep 20, 2026

26views this month

Maintenance

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

Slowing36% signal

last push 213d ago · last release Nov 13, 2025

+30 stars (30d) · +8 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 691303110
  • Not a fork
  • Verified publisher: organization account
  • Computed Sep 20, 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
Last query
Jul 15, 2026
Scanner
osv@v1
Stored findings
9
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-4x5r-pxfx-6jf8
@babel/core@7.23.7 · osv@v1
package-lock.json
GHSA-968p-4wvh-cqc8
@babel/helpers@7.23.8 · osv@v1
package-lock.json
GHSA-f886-m6hf-6m8v
brace-expansion@2.0.1 · osv@v1
package-lock.json
GHSA-v6h2-p8h4-qcjw
brace-expansion@2.0.1 · osv@v1
package-lock.json
GHSA-23c5-xmqv-rm74
minimatch@5.1.6 · osv@v1
package-lock.json
GHSA-3ppc-4f35-3m26
minimatch@5.1.6 · osv@v1
package-lock.json
GHSA-7r86-cg39-jmmj
minimatch@5.1.6 · osv@v1
package-lock.json
GHSA-2g4f-4pwh-qvx6
ajv@6.12.6 · osv@v1
package-lock.json
GHSA-grv7-fg5c-xmjg
braces@3.0.2 · osv@v1
package-lock.json

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/ollama-ollama-js/trust.

Common questions

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