@openeuropa/bcl-subscription
OE - BCL subscription
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy ended with a legitimate maintainer transition on the OpenEuropa org; 185 versions in registry supports ongoing active project. | ai | |
| provenance | no-provenance | AI (provenance): Established EC open-source monorepo; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 1.21.1 | 1 / 0 | |
| 1.13.2 | 1 / 0 | |
| 1.13.1 | 1 / 0 | |
| 1.13.0 | 1 / 0 | |
| 1.12.0 | 1 / 0 | |
| 1.11.0 | 1 / 0 | |
| 1.10.11 | 1 / 0 | |
| 1.10.10 | 1 / 0 | |
| 1.10.9 | 1 / 0 | |
| 1.10.8 | 1 / 0 | |
| 1.10.7 | 1 / 0 | |
| 1.10.6 | 1 / 0 | |
| 1.10.5 | 1 / 0 | |
| 1.10.4 | 1 / 0 | |
| 1.10.3 | 1 / 0 | |
| 1.10.2 | 1 / 0 | |
| 1.10.1 | 1 / 0 | |
| 1.10.0 | 1 / 0 | |
| 1.9.2 | 1 / 0 | |
| 1.9.1 | 1 / 0 | |
| 1.9.0 | 1 / 0 | |
| 1.8.2 | 1 / 0 | |
| 1.8.0 | 1 / 0 | |
| 1.7.0 | 1 / 0 | |
| 1.6.0 | 1 / 0 | |
| 1.5.0 | 1 / 0 | |
| 1.4.0 | 1 / 0 | |
| 1.3.0 | 1 / 0 | |
| 1.2.2 | 1 / 0 | |
| 0.4748.202605190849 | 1 / 0 | |
| 0.4746.202605131300 | 1 / 0 | |
| 0.4643.202604220950 | 1 / 0 | |
| 0.4643.202604212251 | 1 / 0 | |
| 0.4643.202604211830 | 1 / 0 | |
| 0.4643.202604101500 | 1 / 0 | |
| 0.4605.202604011400 | 1 / 0 | |
| 0.4590.202603131800 | 1 / 0 | |
| 0.4590.202603131200 | 1 / 0 | |
| 0.4499.202603051100 | 1 / 0 | |
| 0.4499.202603041330 | 1 / 0 | |
| 0.4499.202603041230 | 1 / 0 | |
| 0.4499.202603041200 | 1 / 0 | |
| 0.4499.202602271530 | 1 / 0 | |
| 0.4499.202602241910 | 1 / 0 | |
| 0.4499.202602232200 | 1 / 0 | |
| 0.4360.202601141610 | 1 / 0 | |
| 0.4298.202511051800 | 1 / 0 | |
| 0.4230.202512021730 | 1 / 0 | |
| 0.4185.202512021245 | 1 / 0 | |
| 0.4185.202511191330 | 1 / 0 | |
| 0.4032.202602121610 | 1 / 0 |
v1.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.