@duetds/cli
This package includes Duet Design System CLI.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @duetds/cli from Duet Design System; no resemblance to 'joi'. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI scaffolding tool; child_process use is expected for running build/copy commands. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 0.0.0.0:3000 in Playwright config template is standard localhost dev-server binding, not malicious. | ai | |
| phantom-deps | phantom-dep:esm | AI (phantom-deps): esm is declared as a runtime dependency and used via config files; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.1.69 | 6 / 0 | |
| 4.1.68 | 6 / 0 | |
| 4.1.66 | 6 / 0 | |
| 4.1.65 | 6 / 0 | |
| 4.1.64 | 6 / 0 | |
| 4.1.63 | 6 / 0 | |
| 4.1.62 | 6 / 0 |
v4.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.68
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2026-05-28, but kasimir-dka is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.