Home/Context-Engine/Trust report

Trust and health report

Context-Engine - trust report

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

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

43views this month

Maintenance

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

Steady60% signal

last push 73d ago · last release Jul 8, 2026 · 2 releases (90d)

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

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 1072561618
  • 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
Oct 11, 2026
Scanner
osv@v1
Stored findings
38
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-p498-v437-472g
@humanfs/node@0.16.7 · osv@v1
package-lock.json
GHSA-29g2-3rmr-qm68
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-2crg-3p73-43xp
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-3f6h-2hrp-w5wx
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-866w-xmhq-wj7x
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-88qp-p4qg-rqm6
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-fpg4-jhqr-589c
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-hgv7-v322-mmgr
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-j2f3-wq62-6q46
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-j62c-4x62-9r35
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-vrhm-gvg7-fpcf
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-wqjv-9729-c5q2
@sveltejs/kit@2.49.3 · osv@v1
package-lock.json
GHSA-3jxr-9vmj-r5cp
brace-expansion@2.0.2 · osv@v1
package-lock.json
GHSA-6j4f-fj2g-mc7p
brace-expansion@2.0.2 · osv@v1
package-lock.json
GHSA-f886-m6hf-6m8v
brace-expansion@2.0.2 · osv@v1
package-lock.json
GHSA-mh99-v99m-4gvg
brace-expansion@2.0.2 · osv@v1
package-lock.json
GHSA-q2hr-2g5m-vwhr
brace-expansion@2.0.2 · osv@v1
package-lock.json
GHSA-qhr7-859c-m2p7
brace-expansion@2.0.2 · osv@v1
package-lock.json
GHSA-rgw5-rvv9-x895
brace-expansion@2.0.2 · osv@v1
package-lock.json
GHSA-23c5-xmqv-rm74
minimatch@9.0.5 · osv@v1
package-lock.json
GHSA-3ppc-4f35-3m26
minimatch@9.0.5 · osv@v1
package-lock.json
GHSA-7r86-cg39-jmmj
minimatch@9.0.5 · osv@v1
package-lock.json
GHSA-2g4f-4pwh-qvx6
ajv@6.12.6 · osv@v1
package-lock.json
GHSA-vfj7-8cjw-p6xm
braces@3.0.3 · osv@v1
package-lock.json
GHSA-pxg6-pf52-xh8x
cookie@0.6.0 · osv@v1
package-lock.json
GHSA-33hq-fvwr-56pm
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-4q55-j62x-fr9h
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-8qm3-746x-r74r
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-9rgm-9g3h-6x36
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-cfw5-2vxh-hr84
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-g2pg-6438-jwpf
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-hx4r-w6wj-j8fg
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-j22f-vq7h-c4qm
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-mcm9-63f2-9j32
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-mwv9-gp5h-frr4
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-r9w8-h9r3-54w4
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-vw5p-8cq8-m7mv
devalue@5.6.1 · osv@v1
package-lock.json
GHSA-wf3x-273g-mvxv
devalue@5.6.1 · 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/context-engine-ai-context-engine/trust.

Common questions

Is Context-Engine maintained?
GraphCanon rates Context-Engine "Steady" (60% maintenance signal from public GitHub metadata, computed Sep 20, 2026). Last push was 73 days ago. 2 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
Is Context-Engine safe to use?
Last scanned Oct 11, 2026 (deps profile). Status: 38 low - 38 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 Context-Engine as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is Context-Engine a fork?
No. Context-Engine is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does Context-Engine have known security vulnerabilities?
Last scanned Oct 11, 2026 (deps profile). Status: 38 low - 38 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 Context-Engine 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 Context-Engine?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for Context-Engine. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for Context-Engine?
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.