create-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@done-coding/cli-inject | AI (phantom-deps): Scoped internal dep referenced in config but bundled at build time; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Chinese-language CLI tool with minimal README; low-value signals don't indicate spam or malice for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.11.22 | 4 / 6 | |
| 0.11.21 | 4 / 6 | |
| 0.11.20 | 4 / 6 | |
| 0.11.19 | 4 / 6 | |
| 0.11.18 | 4 / 6 | |
| 0.11.2 | 4 / 6 | |
| 0.11.1 | 4 / 6 | |
| 0.10.3 | 4 / 6 |
v0.11.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.