@jpp-toolkit/cli
CLI tool for JS/TS project development workflows.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @jpp-toolkit/cli; Levenshtein match to 'joi' is a false positive with no brand impersonation intent. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): oclif plugins are loaded via oclif config, not direct imports; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@jpp-toolkit/plugin-lint | AI (phantom-deps): oclif plugin loaded via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jpp-toolkit/plugin-clean | AI (phantom-deps): oclif plugin loaded via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jpp-toolkit/plugin-build-lib | AI (phantom-deps): oclif plugin loaded via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jpp-toolkit/plugin-changesets | AI (phantom-deps): oclif plugin loaded via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jpp-toolkit/plugin-build-fivem | AI (phantom-deps): oclif plugin loaded via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jpp-toolkit/plugin-build-react | AI (phantom-deps): oclif plugin loaded via config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jpp-toolkit/plugin-check-updates | AI (phantom-deps): oclif plugin loaded via config, not direct import; stable false positive. | ai |
Versions (showing 10 of 214)
| Version | Deps | Published |
|---|---|---|
| 0.0.20 | 8 / 2 | |
| 0.0.19 | 8 / 2 | |
| 0.0.18 | 8 / 2 | |
| 0.0.17 | 8 / 2 | |
| 0.0.16 | 7 / 2 | |
| 0.0.15 | 7 / 2 | |
| 0.0.14 | 7 / 2 | |
| 0.0.13 | 7 / 2 | |
| 0.0.12 | 7 / 2 | |
| 0.0.11 | 7 / 2 |
v0.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.