← Home

@done-coding/cli-publish

npm Repository Homepage

项目发布命令行工具

36
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

justsosu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@done-coding/node-tools AI (dependencies): First-party sibling package within the same org's monorepo. ai
publish-pattern new-deps-added AI (publish-pattern): uuid is a well-known, widely-used package with no malicious history; addition is benign. ai

Versions (showing 36 of 36)

Version Deps Published
0.8.5 2 / 8
0.8.4 2 / 7
0.8.3 2 / 7
0.8.2 2 / 7
0.8.1 2 / 7
0.8.0 2 / 7
0.7.16 2 / 7
0.7.15 2 / 7
0.7.13 2 / 8
0.7.12 2 / 8
0.7.11 3 / 9
0.7.10 3 / 9
0.7.8 3 / 9
0.7.7 3 / 9
0.7.6 3 / 9
0.7.5 3 / 9
0.7.3 3 / 9
0.7.2 3 / 9
0.7.0 3 / 9
0.5.5 3 / 9
0.5.4 3 / 9
0.5.3 3 / 9
0.5.2 3 / 9
0.4.4 6 / 10
0.4.3 5 / 10
0.4.2 5 / 10
0.4.1 5 / 10
0.4.0 5 / 10
0.3.7 5 / 10
0.3.6 5 / 10
0.3.5 5 / 10
0.3.4 5 / 10
0.3.3 5 / 10
0.3.2 5 / 10
0.3.0 5 / 10
0.2.0 5 / 10

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.7

1 finding
LOW No provenance attestation provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.5

1 finding
LOW No provenance attestation provenance

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

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

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