← Home

@cleocode/cant

npm Repository Homepage

CANT protocol parser and runtime for CLEO — wraps cant-core via napi-rs

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

kryptobaseddev

Keywords

cleocantagentparsernapi-rs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; repo URL unchanged, consistent with intentional CI/CD automation by the original maintainer. ai
phantom-deps phantom-dep:@cleocode/contracts AI (phantom-deps): @cleocode/contracts is a same-org declared runtime dep; phantom detection likely reflects indirect/type-only usage rather than a real missing dependency. ai

Versions (showing 5 of 5)

Version Deps Published
2026.4.5 2 / 2
2026.4.4 2 / 2
2026.4.1 2 / 2
2026.4.0 2 / 2
2026.3.76 2 / 2

v2026.4.5

2 findings
HIGH Publisher changed: kryptobaseddev → GitHub Actions (on 2026-04-07) provenance

This version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.

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.

v2026.4.4

2 findings
HIGH Publisher changed: kryptobaseddev → GitHub Actions (on 2026-04-07) provenance

This version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.

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.

v2026.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2026.4.0

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.

v2026.3.76

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.