← Home

@done-coding/cli-component

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
publish-pattern new-deps-added AI (publish-pattern): New dep is same-org package replacing lodash utilities; consistent with internal refactor pattern for this package family. ai
provenance no-provenance AI (provenance): Consistent across all 59 versions; org does not use Sigstore attestation. ai

Versions (showing 36 of 36)

Version Deps Published
0.6.1 2 / 8
0.6.0 2 / 8
0.5.4 7 / 11
0.5.3 7 / 11
0.5.2 7 / 11
0.5.1 7 / 11
0.5.0 7 / 11
0.4.12 7 / 11
0.4.11 7 / 11
0.4.9 7 / 12
0.4.8 7 / 12
0.4.7 7 / 12
0.4.6 7 / 12
0.4.5 7 / 12
0.4.4 7 / 12
0.4.2 7 / 12
0.4.1 7 / 12
0.4.0 7 / 12
0.3.11 7 / 12
0.3.10 7 / 12
0.3.8 7 / 12
0.3.6 7 / 12
0.3.5 7 / 12
0.3.4 7 / 12
0.3.3 7 / 12
0.2.2 12 / 16
0.2.1 12 / 16
0.2.0 12 / 16
0.1.8 12 / 16
0.1.7 12 / 16
0.1.6 12 / 16
0.1.5 12 / 16
0.1.4 12 / 16
0.1.3 12 / 16
0.1.2 12 / 16
0.1.1 12 / 16

v0.2.2

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.2.1

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.2.0

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.8

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

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.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
INFO No provenance attestation provenance

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

v0.1.2

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

1 finding
INFO No provenance attestation provenance

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