node-releases
Node.js releases data
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transition to 'ai' (Andrey Sitnik), a highly trusted publisher who maintains the browserslist ecosystem that depends on this package. | ai |
Versions (showing 51 of 117)
| Version | Deps | Published |
|---|---|---|
| 2.0.51 | 0 / 1 | |
| 2.0.50 | 0 / 1 | |
| 2.0.49 | 0 / 1 | |
| 2.0.48 | 0 / 1 | |
| 2.0.47 | 0 / 1 | |
| 2.0.46 | 0 / 1 | |
| 2.0.45 | 0 / 1 | |
| 2.0.44 | 0 / 1 | |
| 2.0.42 | 0 / 1 | |
| 2.0.38 | 0 / 1 | |
| 2.0.37 | 0 / 1 | |
| 2.0.36 | 0 / 1 | |
| 2.0.27 | 0 / 1 | |
| 2.0.26 | 0 / 1 | |
| 2.0.25 | 0 / 1 | |
| 2.0.23 | 0 / 1 | |
| 2.0.21 | 0 / 1 | |
| 2.0.20 | 0 / 1 | |
| 2.0.19 | 0 / 1 | |
| 2.0.18 | 0 / 1 | |
| 2.0.17 | 0 / 1 | |
| 2.0.14 | 0 / 1 | |
| 2.0.13 | 0 / 1 | |
| 2.0.12 | 0 / 1 | |
| 2.0.11 | 0 / 1 | |
| 2.0.10 | 0 / 1 | |
| 2.0.9 | 0 / 1 | |
| 2.0.8 | 0 / 1 | |
| 2.0.7 | 0 / 1 | |
| 2.0.6 | 0 / 1 | |
| 2.0.5 | 0 / 1 | |
| 2.0.4 | 0 / 1 | |
| 2.0.3 | 0 / 1 | |
| 2.0.2 | 0 / 1 | |
| 2.0.1 | 0 / 1 | |
| 2.0.0 | 0 / 1 | |
| 1.1.77 | 0 / 1 | |
| 1.1.76 | 0 / 1 | |
| 1.1.75 | 0 / 1 | |
| 1.1.74 | 0 / 1 | |
| 1.1.73 | 0 / 1 | |
| 1.1.72 | 0 / 1 | |
| 1.1.71 | 0 / 1 | |
| 1.1.70 | 0 / 1 | |
| 1.1.69 | 0 / 1 | |
| 1.1.68 | 0 / 1 | |
| 1.1.67 | 0 / 1 | |
| 1.1.66 | 0 / 1 | |
| 1.1.65 | 0 / 1 | |
| 1.1.64 | 0 / 1 | |
| 1.1.63 | 0 / 1 |
v2.0.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.