---
title: "kereva-scanner trust report"
type: "trust-report"
slug: "kereva-dev-kereva-scanner"
canonical_url: "https://www.graphcanon.com/tools/kereva-dev-kereva-scanner/trust"
computed_at: "2026-07-15T10:39:48.189Z"
maintenance_label: "Dormant"
security_status: "findings"
---

# kereva-scanner trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and external security intelligence providers. Not a security guarantee._

## Maintenance

- Label: Dormant (18% recency signal)
- Days since last push: 464
- Last release: 2025-03-14T19:26:27Z
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 948686788
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-15T10:39:48.189Z
- Methodology: github_public_v1

## Security intelligence

- **OSV dependency advisories**: Published findings
  - Last query: 2026-07-15T10:39:49.90174+00:00
  - Evidence: https://osv.dev/
- **deps.dev advisories**: Not queried
  - Evidence: https://deps.dev/
- **OpenSSF Scorecard**: Not queried
  - Evidence: https://api.securityscorecards.dev/projects/github.com/kereva-dev/kereva-scanner
  - Note: Weekly public scans omit some checks at scale.

### Findings

- **low**: GHSA-6w46-j5rx-g56g (pytest@7.0.0 · requirements.txt · osv@v1)
- **low**: PYSEC-2026-1845 (pytest@7.0.0 · requirements.txt · osv@v1)

## Method and caveats

These are heuristics from public GitHub data and external security intelligence providers, sourced and dated. 
"No published findings from this source" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is kereva-scanner maintained?

GraphCanon rates kereva-scanner "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 464 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is kereva-scanner safe to use?

Last scanned today (deps profile). Status: 2 low - 2 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 kereva-scanner as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is kereva-scanner a fork?

No. kereva-scanner is not flagged as a fork in GitHub metadata at the time of the last refresh.

### Does kereva-scanner have known security vulnerabilities?

Last scanned today (deps profile). Status: 2 low - 2 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 kereva-scanner trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).

### What does GraphCanon never claim about kereva-scanner?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for kereva-scanner. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology).

### How does GraphCanon assess trust for kereva-scanner?

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](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/kereva-dev-kereva-scanner/trust`](/api/graphcanon/tools/kereva-dev-kereva-scanner/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_