← Home

@websolutespa/bom-mixer-llm

7
Versions
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

websolute-adminactariancbrualdiamacafedericodilucagiacomo_grassettim.fortarmy75ldeblasio

Keywords

bommixerllm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-peer-dep:lenis AI (dependencies): Peer dependency pattern standard for React libraries; consumer controls version. ai
provenance no-provenance AI (provenance): Established publisher with long track record; lack of provenance is common and not a risk signal here. ai
dependencies unvetted-dep:nanogl AI (dependencies): nanogl is a legitimate WebGL library; stable dependency for this UI package. ai

Versions (showing 7 of 7)

Version Deps Published
1.10.6 2 / 21
1.10.4 2 / 21
1.10.3 2 / 21
1.10.1 2 / 21
1.9.3 2 / 20
1.9.0 2 / 20
1.8.38 2 / 19

v1.10.4

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.

v1.10.3

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.

v1.10.1

1 finding
INFO No provenance attestation provenance

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

v1.9.3

1 finding
INFO No provenance attestation provenance

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

v1.9.0

1 finding
INFO No provenance attestation provenance

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

v1.8.38

1 finding
INFO No provenance attestation provenance

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