← Home

@openeuropa/bcl-theme-default

npm Repository Homepage

OE - BCL theme default

19
Versions
EUPL-1.2
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

planctustiberiu.dumitru23moises.rodriguezpiotrsmykaj

Keywords

openeuropabootstrap-component-librarydesign-systemtwig

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): piotrsmykaj is an established publisher (121 approved) within the openeuropa org; transition appears legitimate. ai

Versions (showing 19 of 19)

Version Deps Published
1.21.1 0 / 13
1.13.0 0 / 13
1.12.0 0 / 13
0.4748.202605190849 0 / 13
0.4746.202605131300 0 / 13
0.4712.202604221445 0 / 13
0.4643.202605061520 0 / 13
0.4643.202605061040 0 / 13
0.4643.202605041650 0 / 13
0.4643.202604221100 0 / 13
0.4643.202604221015 0 / 13
0.4643.202604221000 0 / 13
0.4643.202604220950 0 / 13
0.4643.202604220900 0 / 13
0.4643.202604212251 0 / 13
0.4643.202604211830 0 / 13
0.4643.202604101500 0 / 14
0.4605.202604011400 0 / 13
0.1.202605251700 0 / 13

v1.21.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: piotrsmykaj → tiberiu.dumitru23 (on 2026-05-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-11. This could indicate a legitimate maintainer transition or an account compromise.

v1.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.0

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4746.202605131300

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4712.202604221445

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4643.202605061520

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4643.202605061040

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4643.202605041650

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tiberiu.dumitru23 → piotrsmykaj (on 2026-05-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.4643.202604221100

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4643.202604221015

2 findings
HIGH Publisher changed: tiberiu.dumitru23 → piotrsmykaj (on 2026-04-22) provenance

This version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4643.202604221000

2 findings
HIGH Publisher changed: tiberiu.dumitru23 → piotrsmykaj (on 2026-04-22) provenance

This version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4643.202604220950

2 findings
HIGH Publisher changed: tiberiu.dumitru23 → piotrsmykaj (on 2026-04-22) provenance

This version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4643.202604220900

2 findings
HIGH Publisher changed: tiberiu.dumitru23 → piotrsmykaj (on 2026-04-22) provenance

This version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4643.202604212251

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4643.202604211830

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4643.202604101500

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4605.202604011400

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.202605251700

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.