@openeuropa/bcl-subscription-block
OE - BCL subscription block
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): New publisher piotrsmykaj has strong track record (219/0) and is part of the same org; consistent with legitimate maintainer rotation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by active publishing from a trusted org publisher; no malicious indicators in content or diff. | ai | |
| phantom-deps | phantom-dep:@openeuropa/bcl-form | AI (phantom-deps): Same-org Twig component; consumed via templates, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@openeuropa/bcl-alert | AI (phantom-deps): Same-org Twig component; consumed via templates, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@openeuropa/bcl-modal | AI (phantom-deps): Same-org Twig component; consumed via templates, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@openeuropa/bcl-button | AI (phantom-deps): Same-org Twig component; consumed via templates, not JS imports. Stable FP for this package. | ai |
Versions (showing 68 of 68)
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.