← Home

@done-coding/cli-ai

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

justsosu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@done-coding/cli-component AI (phantom-deps): Same-org sibling package; dynamic/lazy loading pattern expected in this monorepo CLI. ai
phantom-deps phantom-dep:create-done-coding AI (phantom-deps): CLI scaffolding tool; referenced in config, not directly imported — stable pattern for this package. ai
phantom-deps phantom-dep:@done-coding/cli-config AI (phantom-deps): Same-org sibling package; dynamic/lazy loading pattern expected in this monorepo CLI. ai
phantom-deps phantom-dep:@done-coding/cli-inject AI (phantom-deps): Same-org sibling package; dynamic/lazy loading pattern expected in this monorepo CLI. ai
phantom-deps phantom-dep:@done-coding/cli-extract AI (phantom-deps): Same-org sibling package; dynamic/lazy loading pattern expected in this monorepo CLI. ai
phantom-deps phantom-dep:@done-coding/cli-publish AI (phantom-deps): Same-org sibling package; dynamic/lazy loading pattern expected in this monorepo CLI. ai
phantom-deps phantom-dep:@done-coding/cli-template AI (phantom-deps): Same-org sibling package; dynamic/lazy loading pattern expected in this monorepo CLI. ai
provenance no-provenance AI (provenance): New package from a small org; lack of provenance is common and no other risk signals present. ai

Versions (showing 7 of 7)

Version Deps Published
0.1.6 10 / 8
0.1.5 10 / 8
0.1.4 10 / 8
0.1.3 2 / 9
0.1.2 2 / 9
0.1.1 2 / 9
0.1.0 2 / 9

v0.1.6

1 finding
INFO No provenance attestation provenance

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

v0.1.5

1 finding
INFO No provenance attestation provenance

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

v0.1.4

1 finding
INFO No provenance attestation provenance

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

v0.1.3

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.

v0.1.2

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.

v0.1.1

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.

v0.1.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.