@inlang/paraglide-js
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): Transition to GitHub Actions publisher is confirmed legitimate by SLSA/Sigstore attestation on this and future versions. | ai | |
| dependencies | unvetted-dep:@inlang/sdk | AI (dependencies): First-party @inlang org dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@inlang/recommend-sherlock | AI (dependencies): First-party @inlang org dependency; stable pattern across all versions of this package. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 2.22.0 | 7 / 17 | |
| 2.21.0 | 7 / 16 | |
| 2.20.2 | 7 / 15 | |
| 2.20.1 | 7 / 15 | |
| 2.20.0 | 7 / 15 | |
| 2.19.0 | 7 / 15 | |
| 2.18.2 | 7 / 15 | |
| 2.18.1 | 7 / 15 | |
| 2.18.0 | 7 / 15 | |
| 2.17.0 | 7 / 15 | |
| 2.16.1 | 7 / 15 | |
| 2.16.0 | 7 / 15 | |
| 2.15.3 | 7 / 15 | |
| 2.15.2 | 7 / 15 | |
| 2.15.1 | 7 / 15 | |
| 2.15.0 | 7 / 15 | |
| 2.14.1 | 7 / 15 | |
| 2.14.0 | 7 / 15 | |
| 2.13.2 | 7 / 15 | |
| 2.13.1 | 7 / 15 | |
| 2.13.0 | 7 / 15 | |
| 2.12.0 | 7 / 15 | |
| 2.11.0 | 7 / 15 | |
| 2.10.0 | 7 / 15 | |
| 2.9.1 | 7 / 15 | |
| 2.9.0 | 7 / 15 | |
| 2.8.0 | 7 / 15 | |
| 2.7.2 | 7 / 15 | |
| 2.7.1 | 7 / 15 | |
| 2.7.0 | 7 / 15 | |
| 2.6.0 | 7 / 15 | |
| 2.5.0 | 7 / 15 | |
| 2.4.0 | 7 / 15 | |
| 2.3.2 | 7 / 17 | |
| 2.3.1 | 7 / 17 | |
| 2.3.0 | 7 / 17 | |
| 2.2.0 | 7 / 18 | |
| 2.1.0 | 7 / 18 | |
| 2.0.13 | 7 / 18 | |
| 2.0.12 | 7 / 18 | |
| 2.0.11 | 7 / 18 | |
| 2.0.10 | 7 / 18 | |
| 2.0.9 | 7 / 18 | |
| 2.0.8 | 7 / 18 | |
| 2.0.7 | 7 / 18 | |
| 2.0.6 | 7 / 18 | |
| 2.0.5 | 7 / 18 | |
| 2.0.4 | 7 / 18 | |
| 2.0.3 | 7 / 18 | |
| 2.0.2 | 7 / 18 | |
| 2.0.1 | 7 / 18 | |
| 2.0.0 | 7 / 18 |
v2.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.20.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.