@balena/env-parsing
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.3.8 | 0 / 11 | |
| 1.3.7 | 0 / 11 | |
| 1.3.6 | 0 / 11 | |
| 1.3.5 | 0 / 11 | |
| 1.3.4 | 0 / 11 | |
| 1.3.3 | 0 / 11 | |
| 1.3.2 | 0 / 11 | |
| 1.3.1 | 0 / 11 | |
| 1.3.0 | 0 / 11 | |
| 1.2.25 | 0 / 11 | |
| 1.2.24 | 0 / 11 | |
| 1.2.23 | 0 / 11 | |
| 1.2.22 | 0 / 11 | |
| 1.2.21 | 0 / 11 | |
| 1.2.20 | 0 / 11 | |
| 1.2.19 | 0 / 11 | |
| 1.2.18 | 0 / 11 | |
| 1.2.17 | 0 / 11 | |
| 1.2.16 | 0 / 11 | |
| 1.2.15 | 0 / 11 | |
| 1.2.14 | 0 / 11 | |
| 1.2.13 | 0 / 11 | |
| 1.2.12 | 0 / 11 | |
| 1.2.11 | 0 / 11 | |
| 1.2.10 | 0 / 11 | |
| 1.2.9 | 0 / 11 | |
| 1.2.8 | 0 / 11 | |
| 1.2.6 | 0 / 11 | |
| 1.2.5 | 0 / 11 | |
| 1.2.4 | 0 / 11 | |
| 1.2.3 | 0 / 11 | |
| 1.2.2 | 0 / 11 | |
| 1.2.1 | 0 / 11 | |
| 1.2.0 | 0 / 11 |
v1.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.