Is open-kritt safe to use?

open-kritt has an HVTrust score of 56.1/100 (Grade C), ranked #568 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for open-kritt?

open-kritt scores 56.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.1k GitHub stars and is categorized under Security & Guardrails.

open-kritt

Kritt-ai/open-kritt

Open-source, self-hosted AI vulnerability research tool that orchestrates agents to find and validate security issues in

Security & Guardrails JavaScript Grade C Listed AGPL-3.0

56.1/100

Rank #568 of 1320

Compare open-kritt

How does it stack up against its Security & Guardrails neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-24 · 11d ago

Recent change

Rank +10

Is open-kritt safe? open-kritt scores 56.1/100 (Grade C), ranked #568 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 38% of recent commits are signed; last pushed 2026-08-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#9 DvalinCode — 56.8 (C) → #10 PentAGI — 56.5 (C) → #12 Agentic Security — 55.9 (C) → #13 LLM Guard — 55.9 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 16 spots (#552 → #568)

2026-09-03

Rank Moved

Rank dropped 38 spots (#514 → #552)

2026-09-02

Rank Moved

Rank dropped 21 spots (#493 → #514)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for open-kritt View Security & Guardrails Report missing data

75.8

Activity sub-score · out of 100

#11

In Security & Guardrails

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-26 2026-09-04

Activity & Reach

Stars

2.1k

Forks

353

Last Push

2026-08-24

11 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼16

was #552

Analysis

HVTrust Dimensions vs Security & Guardrails

56.1 / 100 · 100.0% confidence

open-kritt Security & Guardrails average (22 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.3 / 25

2.9 below avg 10.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.3 below avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.7

Maintenance60% last-push freshness · 40% commit activity

17.8 / 20

1.6 above avg 16.2

AdoptionLog-scaled stars · package downloads

8.0 / 20

1.6 below avg 9.6

Activity Inputs

75.8 / 100

StarsRepository reach

19.9 / 30

FreshnessLast push recency

23.5 / 25

ActivityRecent commits

20.5 / 25

CommunityFork signal

11.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 2, 2026

Signed Commits

38%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 2

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 1

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 4

Is open-kritt safe?

open-kritt has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does open-kritt publish package provenance?

No published build provenance is currently detected for open-kritt. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does open-kritt have an OpenSSF Scorecard?

open-kritt has an OpenSSF Scorecard score of 4.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is open-kritt actively maintained?

Maintained. Last push was 11 days ago.

What license does open-kritt use?

open-kritt ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are open-kritt's commits signed?

37% of the last 100 commits to open-kritt are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain open-kritt?

For maintainers

HVTrust scores open-kritt from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-04

Rank Moved

Rank dropped 16 spots (#552 → #568)

2026-09-03

Rank Moved

Rank dropped 38 spots (#514 → #552)

2026-09-02

Rank Moved

Rank dropped 21 spots (#493 → #514)

2026-09-01

Rank Moved

Rank dropped 19 spots (#474 → #493)

2026-08-31

Rank Moved

Rank dropped 28 spots (#446 → #474)

2026-08-30

Scorecard Added

OSSF Scorecard: 4.3/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 629 spots (#1075 → #446)

2026-08-30

HVTrust Changed

HVTrust up 33.0pts (24.0 → 57.0)

2026-08-29

Rank Moved

Rank dropped 49 spots (#1026 → #1075)

2026-08-28

Rank Moved

Rank dropped 33 spots (#993 → #1026)

2026-08-27

Rank Moved

Rank dropped 27 spots (#966 → #993)

2026-08-26

Newly Listed

First tracked at rank #966

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/open-kritt.svg)](https://hvtracker.net/agents/open-kritt)
            
HTML:
            <a href="https://hvtracker.net/agents/open-kritt"><img src="https://hvtracker.net/badge/open-kritt.svg" alt="HVTrust"></a>

Other agents in Security & Guardrails

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON