@cleocode/runtime — Greenflagged

Long-running process layer for CLEO — agent polling, SSE connections, heartbeat, key rotation

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

kryptobaseddev

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/gateway/index.d.ts	AI (source-diff): Long single-line TypeScript barrel re-export in .d.ts; not obfuscated code, stable pattern for this bundled package.	ai	2026/06/01
dependencies	unvetted-dep:@cleocode/core	AI (dependencies): Sibling package in the same @cleocode monorepo, published at the same version via the same CI/CD pipeline with SLSA provenance. Unvetted status is a registry artifact, not a risk signal.	ai	2026/04/25
dependencies	unvetted-dep:@cleocode/contracts	AI (dependencies): Sibling package in the same @cleocode monorepo, published at the same version via the same CI/CD pipeline with SLSA provenance. Unvetted status is a registry artifact, not a risk signal.	ai	2026/04/25

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.