@done-coding/cli
done-coding命令行工具
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@done-coding/cli-init | AI (dependencies): Same-org sibling package, part of monorepo split, not third-party. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party sibling packages under same npm org. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Used via config reference, heuristic false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @done-coding/cli is not a typosquat of joi; Levenshtein match is a false positive. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs node es/postinstall.mjs; consistent with CLI tool setup across 91 versions. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 10 / 4 | |
| 0.15.22 | 9 / 4 | |
| 0.15.21 | 9 / 4 | |
| 0.15.19 | 9 / 5 | |
| 0.15.18 | 9 / 5 | |
| 0.15.17 | 9 / 5 | |
| 0.15.16 | 9 / 5 | |
| 0.15.12 | 9 / 5 | |
| 0.15.6 | 9 / 5 | |
| 0.15.0 | 9 / 5 | |
| 0.14.5 | 9 / 5 | |
| 0.14.4 | 9 / 5 | |
| 0.14.3 | 9 / 5 | |
| 0.14.1 | 9 / 5 | |
| 0.14.0 | 9 / 5 | |
| 0.13.3 | 8 / 5 | |
| 0.11.2 | 10 / 7 | |
| 0.11.1 | 10 / 7 | |
| 0.11.0 | 10 / 7 | |
| 0.10.0 | 9 / 7 | |
| 0.9.1 | 9 / 7 | |
| 0.9.0 | 9 / 7 | |
| 0.8.1 | 9 / 7 | |
| 0.8.0 | 9 / 7 | |
| 0.7.0 | 9 / 7 | |
| 0.6.0 | 9 / 7 | |
| 0.5.0 | 9 / 7 | |
| 0.4.2 | 9 / 7 | |
| 0.4.1 | 9 / 7 | |
| 0.3.1 | 7 / 7 | |
| 0.3.0 | 7 / 7 | |
| 0.2.0 | 6 / 7 | |
| 0.1.0 | 5 / 7 |
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.