@openeuropa/bcl-project-status
OE - BCL project status
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): piotrsmykaj is an established publisher (219 approved) within the same org; transition appears legitimate. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Multiple same-day releases by the new publisher indicate a coordinated org migration, not a takeover. | ai | |
| phantom-deps | phantom-dep:@openeuropa/bcl-badge | AI (phantom-deps): Same-org scoped dependency; likely re-exported or indirect use pattern. | ai | |
| phantom-deps | phantom-dep:@openeuropa/bcl-heading | AI (phantom-deps): Same-org scoped dependency; likely re-exported or indirect use pattern. | ai | |
| phantom-deps | phantom-dep:@openeuropa/bcl-progress | AI (phantom-deps): Same-org scoped dependency; likely re-exported or indirect use pattern. | ai |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 1.21.1 | 3 / 0 | |
| 1.13.2 | 3 / 0 | |
| 1.13.1 | 3 / 0 | |
| 1.13.0 | 3 / 0 | |
| 1.12.0 | 3 / 0 | |
| 1.11.0 | 3 / 0 | |
| 1.10.11 | 3 / 0 | |
| 1.10.10 | 3 / 0 | |
| 1.10.9 | 3 / 0 | |
| 1.10.8 | 3 / 0 | |
| 1.10.7 | 3 / 0 | |
| 1.10.6 | 3 / 0 | |
| 1.10.5 | 3 / 0 | |
| 1.10.4 | 3 / 0 | |
| 1.10.3 | 3 / 0 | |
| 1.10.2 | 3 / 0 | |
| 1.10.1 | 3 / 0 | |
| 1.10.0 | 3 / 0 | |
| 1.9.2 | 3 / 0 | |
| 1.9.1 | 3 / 0 | |
| 1.9.0 | 3 / 0 | |
| 1.8.2 | 3 / 0 | |
| 1.8.0 | 3 / 0 | |
| 1.7.0 | 3 / 0 | |
| 1.6.0 | 3 / 0 | |
| 1.5.0 | 3 / 0 | |
| 1.4.0 | 3 / 0 | |
| 1.3.0 | 3 / 0 | |
| 1.2.2 | 3 / 0 | |
| 0.4748.202605190849 | 3 / 0 | |
| 0.4746.202605131300 | 3 / 0 | |
| 0.4712.202604221445 | 3 / 0 | |
| 0.4643.202605061520 | 3 / 0 | |
| 0.4643.202605061040 | 3 / 0 | |
| 0.4643.202605041650 | 3 / 0 | |
| 0.4643.202604221100 | 3 / 0 | |
| 0.4643.202604221015 | 3 / 0 | |
| 0.4643.202604221000 | 3 / 0 | |
| 0.4643.202604220950 | 3 / 0 | |
| 0.4643.202604220900 | 3 / 0 | |
| 0.4643.202604212251 | 3 / 0 | |
| 0.4643.202604211830 | 3 / 0 | |
| 0.4643.202604101500 | 3 / 0 | |
| 0.4605.202604011400 | 3 / 0 | |
| 0.4590.202603131800 | 3 / 0 | |
| 0.4590.202603131200 | 3 / 0 | |
| 0.4499.202603051100 | 3 / 0 | |
| 0.4499.202603041330 | 3 / 0 | |
| 0.4499.202603041230 | 3 / 0 | |
| 0.4499.202603041200 | 3 / 0 | |
| 0.4499.202602271530 | 3 / 0 |
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.