---
title: "kapitan trust report"
type: "trust-report"
slug: "kapicorp-kapitan"
canonical_url: "https://www.graphcanon.com/tools/kapicorp-kapitan/trust"
computed_at: "2026-07-15T10:51:51.591Z"
maintenance_label: "Active"
security_status: "no_lockfile"
---

# kapitan 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: Active (82% recency signal)
- Days since last push: 11
- Last release: 2026-07-03T15:08:46Z
- Releases (90d): 6
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 106306056
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-15T10:51:51.591Z
- Methodology: github_public_v1

## Security intelligence

- **OSV dependency advisories**: No lockfile (source not queried)
  - Last query: 2026-07-15T10:51:52.97831+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/kapicorp/kapitan
  - Note: Weekly public scans omit some checks at scale.

## 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 kapitan maintained?

GraphCanon rates kapitan "Active" (82% maintenance signal from public GitHub metadata, computed today). Last push was 11 days ago. 6 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is kapitan safe to use?

Last scanned today (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see [trust methodology](/trust-methodology) for scope limits. GraphCanon does not certify kapitan as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is kapitan a fork?

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

### Does kapitan have known security vulnerabilities?

Last scanned today (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see [trust methodology](/trust-methodology) for scope limits.

### How often is the kapitan 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 kapitan?

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

### How does GraphCanon assess trust for kapitan?

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/kapicorp-kapitan/trust`](/api/graphcanon/tools/kapicorp-kapitan/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/_