@trapar-waves/cli-template
A CLI template with TypeScript, tsup, consola, destr, and picocolors, offering efficient builds, logging, data parsing, and colorful output, with ESLint for quality.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs 'husky' for git hooks setup; standard dev-tooling pattern in template packages. | ai | |
| phantom-deps | phantom-dep:destr | AI (phantom-deps): destr is a declared runtime dependency and explicitly listed in the package description; stable false positive. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): picocolors is a declared runtime dependency and explicitly listed in the package description; stable false positive. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 3 / 8 | |
| 1.1.17 | 3 / 8 | |
| 1.1.0 | 3 / 8 | |
| 1.0.9 | 3 / 6 | |
| 1.0.8 | 3 / 5 | |
| 1.0.7 | 3 / 5 | |
| 1.0.6 | 3 / 5 | |
| 1.0.5 | 3 / 5 | |
| 1.0.4 | 3 / 5 | |
| 1.0.3 | 3 / 5 |
v1.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.