@openeuropa/bcl-builder
Bootstrap Component Library builder
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Config-file loader pattern; user supplies the path, not arbitrary remote code. Stable for this CLI builder. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): Referenced in config files, not directly imported; expected for a build tool. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped, loaded by convention via @rollup/plugin-babel. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Referenced in config files for bundling; not a direct import. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-replace | AI (phantom-deps): Loaded by convention via rollup plugin system; stable false positive. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-commonjs | AI (phantom-deps): Loaded by convention via rollup plugin system; stable false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.21.1 | 19 / 0 | |
| 1.13.1 | 19 / 0 | |
| 1.13.0 | 19 / 0 | |
| 1.12.0 | 19 / 0 | |
| 1.11.0 | 19 / 0 | |
| 0.4748.202605190849 | 19 / 0 | |
| 0.4746.202605131300 | 19 / 0 | |
| 0.4712.202604221445 | 19 / 0 | |
| 0.4643.202605061520 | 19 / 0 | |
| 0.4643.202605061040 | 19 / 0 | |
| 0.4643.202605041650 | 19 / 0 | |
| 0.4643.202604221100 | 19 / 0 | |
| 0.4643.202604221015 | 19 / 0 | |
| 0.4643.202604221000 | 19 / 0 | |
| 0.4643.202604220950 | 19 / 0 | |
| 0.4643.202604220900 | 19 / 0 | |
| 0.4643.202604212251 | 19 / 0 | |
| 0.4643.202604211830 | 19 / 0 | |
| 0.4643.202604101500 | 19 / 0 | |
| 0.4605.202604011400 | 19 / 0 | |
| 0.4590.202603131800 | 19 / 0 | |
| 0.4590.202603131200 | 19 / 0 | |
| 0.1.202605251700 | 19 / 0 |
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.
v1.11.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.202605061520
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (piotrsmykaj) than the most recent previously approved version (tiberiu.dumitru23) on 2026-05-06, but piotrsmykaj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4643.202605061040
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (piotrsmykaj) than the most recent previously approved version (tiberiu.dumitru23) on 2026-05-06, but piotrsmykaj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4643.202605041650
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (piotrsmykaj) than the most recent previously approved version (tiberiu.dumitru23) on 2026-05-04, but piotrsmykaj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.4643.202604220900
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4590.202603131800
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4590.202603131200
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.