@openeuropa/bcl-data-header
OE header data
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): European Commission org package; provenance absence is consistent across all versions of this package family. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.21.1 | 2 / 0 | |
| 1.13.1 | 2 / 0 | |
| 1.13.0 | 2 / 0 | |
| 1.12.0 | 2 / 0 | |
| 1.11.0 | 2 / 0 | |
| 1.10.11 | 2 / 0 | |
| 1.10.10 | 2 / 0 | |
| 1.10.9 | 2 / 0 | |
| 1.10.1 | 2 / 0 | |
| 0.4748.202605190849 | 2 / 0 | |
| 0.4746.202605131300 | 2 / 0 | |
| 0.4643.202604211830 | 2 / 0 | |
| 0.4643.202604101500 | 2 / 0 | |
| 0.4605.202604011400 | 2 / 0 | |
| 0.4590.202603131800 | 2 / 0 | |
| 0.4590.202603131200 | 2 / 0 | |
| 0.4499.202603051100 | 2 / 0 | |
| 0.4499.202603041330 | 2 / 0 | |
| 0.4499.202603041230 | 2 / 0 | |
| 0.4499.202603041200 | 2 / 0 | |
| 0.4499.202602271530 | 2 / 0 | |
| 0.4499.202602241910 | 2 / 0 | |
| 0.4499.202602232200 | 2 / 0 | |
| 0.4360.202601141610 | 2 / 0 | |
| 0.4298.202511051800 | 2 / 0 | |
| 0.4230.202512021730 | 2 / 0 | |
| 0.4185.202512021245 | 2 / 0 | |
| 0.4185.202511191330 | 2 / 0 | |
| 0.4032.202602121610 | 2 / 0 | |
| 0.4032.202602052130 | 2 / 0 | |
| 0.4032.202602051815 | 2 / 0 | |
| 0.4032.202602051800 | 2 / 0 | |
| 0.4032.202602051715 | 2 / 0 | |
| 0.4032.202602042100 | 2 / 0 | |
| 0.3732.202601071600 | 2 / 0 | |
| 0.1.202605251700 | 2 / 0 | |
| 0.1.202603061200 | 2 / 0 | |
| 0.1.202601141030 | 2 / 0 |
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package 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.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4748.202605190849
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4746.202605131300
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4643.202604211830
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4643.202604101500
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4605.202604011400
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4590.202603131800
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4590.202603131200
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4499.202603051100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4499.202603041330
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4499.202603041230
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4499.202603041200
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4499.202602271530
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4499.202602241910
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4499.202602232200
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4360.202601141610
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4298.202511051800
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4230.202512021730
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4185.202512021245
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4185.202511191330
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4032.202602121610
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4032.202602052130
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4032.202602051815
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4032.202602051800
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4032.202602051715
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4032.202602042100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3732.202601071600
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.202605251700
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.202603061200
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.202601141030
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.