@done-coding/cli MIT 16 versions

@done-coding/cli

npm Repository Homepage

done-coding命令行工具

16

Versions

MIT

License

Yes

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.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped package @done-coding/cli is not a typosquat of joi; Levenshtein match is a false positive.	ai	2026/05/29
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall runs node es/postinstall.mjs; consistent with CLI tool setup across 91 versions.	ai	2026/05/29

Versions (showing 16 of 16)

Version	Deps	Published
0.16.0	10 / 4	2026-04-26
0.15.22	9 / 4	2026-04-12
0.15.21	9 / 4	2026-04-01
0.15.19	9 / 5	2026-01-11
0.15.18	9 / 5	2026-01-10
0.15.17	9 / 5	2026-01-10
0.15.16	9 / 5	2025-12-14
0.15.12	9 / 5	2025-08-27
0.15.6	9 / 5	2025-06-29
0.15.0	9 / 5	2025-06-21
0.14.5	9 / 5	2025-06-16
0.14.4	9 / 5	2025-06-11
0.14.3	9 / 5	2025-06-09
0.14.1	9 / 5	2025-06-08
0.14.0	9 / 5	2025-06-08
0.13.3	8 / 5	2025-06-03

v0.16.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.mjs

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

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.mjs

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

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node scripts/postinstall.mjs

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

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node es/postinstall.mjs

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

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node es/postinstall.mjs

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

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node es/postinstall.mjs

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

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node es/postinstall.mjs

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

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: node es/postinstall.mjs

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

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.5

1 finding

LOW No provenance attestation provenance

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

v0.14.4

1 finding

LOW No provenance attestation provenance

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

v0.14.3

1 finding

LOW No provenance attestation provenance

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

v0.14.1

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

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