@csszyx/cli
Command-line tools for csszyx
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/types | AI (phantom-deps): Babel packages loaded by convention in build tool; stable pattern. | ai | |
| phantom-deps | phantom-dep:@babel/parser | AI (phantom-deps): Babel packages loaded by convention in build tool; stable pattern. | ai | |
| phantom-deps | phantom-dep:@babel/traverse | AI (phantom-deps): Babel packages loaded by convention in build tool; stable pattern. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @csszyx/cli is a scoped package for the csszyx project; Levenshtein match to 'joi' is coincidental. | ai | |
| phantom-deps | phantom-dep:@babel/generator | AI (phantom-deps): @babel/generator is listed as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.9.10 | 14 / 6 | |
| 0.9.9 | 14 / 6 | |
| 0.9.8 | 14 / 6 | |
| 0.9.7 | 14 / 6 | |
| 0.9.6 | 14 / 6 | |
| 0.9.5 | 14 / 6 | |
| 0.9.4 | 14 / 6 | |
| 0.9.3 | 14 / 6 | |
| 0.9.2 | 14 / 6 | |
| 0.9.1 | 14 / 6 | |
| 0.9.0 | 13 / 8 | |
| 0.8.0 | 13 / 8 | |
| 0.7.0 | 13 / 8 | |
| 0.6.2 | 13 / 8 | |
| 0.6.0 | 13 / 8 | |
| 0.5.0 | 13 / 8 | |
| 0.4.0 | 13 / 8 | |
| 0.3.1 | 13 / 8 | |
| 0.3.0 | 13 / 8 | |
| 0.2.0 | 13 / 8 | |
| 0.1.3 | 13 / 8 | |
| 0.1.2 | 13 / 8 | |
| 0.1.1 | 13 / 8 | |
| 0.1.0 | 13 / 8 |
v0.9.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
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.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.2
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.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.