@openeuropa/bcl-theme-joinup
OE - BCL theme joinup
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.21.1 | 0 / 19 | |
| 1.13.1 | 0 / 19 | |
| 1.13.0 | 0 / 19 | |
| 1.12.0 | 0 / 19 | |
| 0.4748.202605190849 | 0 / 19 | |
| 0.4746.202605131300 | 0 / 19 | |
| 0.4712.202604221445 | 0 / 19 | |
| 0.4643.202604221100 | 0 / 19 | |
| 0.4643.202604221015 | 0 / 19 | |
| 0.4643.202604221000 | 0 / 19 | |
| 0.4643.202604220950 | 0 / 19 | |
| 0.4643.202604220900 | 0 / 19 | |
| 0.4643.202604212251 | 0 / 19 | |
| 0.4643.202604211830 | 0 / 19 | |
| 0.4643.202604101500 | 0 / 19 | |
| 0.4605.202604011400 | 0 / 19 | |
| 0.1.202605251700 | 0 / 19 |
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4748.202605190849
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4746.202605131300
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4712.202604221445
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4643.202604221100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4643.202604221015
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4643.202604221000
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4643.202604220950
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4643.202604220900
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4643.202604212251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4643.202604211830
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4643.202604101500
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4605.202604011400
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.202605251700
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.