@nice-move/all-in-base
[![npm][npm-badge]][npm-url] [![github][github-badge]][github-url] ![node][node-badge]
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:@nice-move/prettier-config | AI (phantom-deps): Config dep from same org scope; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@nice-move/cli | AI (phantom-deps): Config/tooling dep from same org scope; not directly imported by design. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 117 versions; package predates common provenance adoption. | ai | |
| dependencies | unvetted-dep:@nice-move/prettier-config | AI (dependencies): Same org scope (@nice-move); stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@nice-move/cli | AI (dependencies): Same org scope (@nice-move); consistent with the package's established dependency pattern. | ai | |
| dependencies | unvetted-dep:@nice-move/tsconfig | AI (dependencies): Same org scope (@nice-move); stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@nice-move/tsconfig | AI (phantom-deps): Re-exported as ./tsconfig entry point; not directly imported in JS but legitimately bundled. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.8.4 | 4 / 0 | |
| 0.8.3 | 4 / 0 | |
| 0.8.2 | 4 / 0 | |
| 0.7.3 | 4 / 0 | |
| 0.6.42 | 4 / 0 | |
| 0.6.41 | 4 / 0 | |
| 0.6.39 | 4 / 0 | |
| 0.6.38 | 4 / 0 | |
| 0.6.36 | 4 / 0 | |
| 0.6.31 | 4 / 0 | |
| 0.6.16 | 4 / 0 | |
| 0.6.15 | 4 / 0 | |
| 0.6.14 | 4 / 0 | |
| 0.6.12 | 4 / 0 | |
| 0.6.10 | 4 / 0 | |
| 0.6.8 | 4 / 0 | |
| 0.6.7 | 4 / 0 | |
| 0.6.1 | 4 / 0 | |
| 0.5.3 | 4 / 0 | |
| 0.5.2 | 4 / 0 | |
| 0.4.32 | 4 / 0 | |
| 0.4.30 | 4 / 0 | |
| 0.4.29 | 4 / 0 | |
| 0.4.25 | 4 / 0 | |
| 0.4.24 | 4 / 0 | |
| 0.4.22 | 4 / 0 |
v0.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.