kusari.dev valid

Kusari

The software supply chain security platform that shows you exactly what's exploitable in your code and ships the fix. Built from source for a complete, provable dependency graph, by the team that co-created the GUAC, SLSA, and in-toto open standards.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T04:52:51.273Z. Cached copy · Source on kusari.dev

# Kusari

> The software supply chain security platform that shows you exactly what's exploitable in your code and ships the fix. Built from source for a complete, provable dependency graph, by the team that co-created the GUAC, SLSA, and in-toto open standards.

## Product

- [Kusari Platform](https://www.kusari.dev/platform/): Command center for supply chain risk. Full transitive graph, reachability, exploitability, and the Kusari Score.
- [Kusari Inspector](https://www.kusari.dev/inspector/): Free autonomous security reviewer in every pull request. Thumbs up or down before code reaches main.
- [Integrations](https://www.kusari.dev/integrations/): Works as the intelligence layer above your existing stack. GitHub, GitLab, Black Duck, Jira, and more.
- [Documentation](https://docs.kusari.cloud): Product docs, setup guides, and API reference.
- [Request a demo](https://www.kusari.dev/demo/): 30-minute walkthrough of the platform against a codebase like yours.

## Why Kusari

- [About Kusari](https://www.kusari.dev/about/): Founded by engineering leaders from finance and government defense who lived the pain of shipping secure software on deadline.
- [Leaders in Open Source](https://www.kusari.dev/open-source/): Founders co-created the open standards now used to secure the industry's supply chains.
- [Financial services](https://www.kusari.dev/industries/finserv/): One dependency graph across the tools you already run, with SBOM and VEX evidence for DORA, NYDFS Part 500, PCI DSS 4.x, and FFIEC examinations.
- [Insurance](https://www.kusari.dev/industries/insurance/): One dependency inventory across claims, policy, and member systems, with SBOM and VEX evidence for NYDFS Part 500, state insurance laws, and HIPAA.
- [Regulated SaaS](https://www.kusari.dev/industries/regulated-saas/): Current SBOM and VEX for every release, built from source, for fintech, insurtech, healthtech, and defensetech vendors facing SOC 2 audits, FedRAMP controls, and customer security reviews.

## Key concepts

- [The 95% problem: transitive dependencies](https://www.kusari.dev/blog/why-transitive-dependencies-biggest-software-supply-chain-blind-spot-2026/): Why standard scanners see only 5% of your real risk.
- [The transitive dependency visibility gap](https://www.kusari.dev/blog/why-72-of-organizations-cant-see-their-real-attack-surface-solving-the-transitive-dependency-visibility-gap/): Why 72% of orgs can't see their real attack surface.
- [Unpacking the Kusari Score](https://www.kusari.dev/blog/kusari-score/): One actionable number from reachability, exploitability, and blast radius, not raw CVSS.
- [Reachability and exploitability analysis](https://www.kusari.dev/blog/improving-vulnerability-reachability-and-exploitability-analysis/): How Kusari traces which vulnerabilities can actually be reached, and writes the VEX.
- [Best SBOM tools](https://www.kusari.dev/blog/best-sbom-tools-2025/): Comparison of SBOM generation tools and how to choose one.

## Regulatory

- [EU
…

Related sites

Explore similar publishers →

Category suggestions: other listed sites in Cybersecurity. These share a category. See the whole category →

Machine-readable: GET /v1/resolve?q=kusari.dev · GET /v1/domain/kusari.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for kusari.dev:
1. POST https://agentwebmap.com/v1/sites/kusari.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://kusari.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/kusari.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/kusari.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.