← Home

@mekari/pixel-airene-float-button

Mekari Pixel | Airene float button component

11
Versions
LGPL-3.0
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jochristiantomkrhelloerwin_mekariaryamekarimekaripackagesdrsuxezakiy_mekaridirgamekarisasmkr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@mekari/pixel-utils AI (dependencies): Internal Mekari monorepo dependency; same publisher namespace, expected for this component package. ai
provenance no-provenance AI (provenance): Mekari org packages consistently lack Sigstore provenance; stable false positive for this publisher. ai

Versions (showing 11 of 11)

Version Deps Published
0.1.10 3 / 2
0.1.9 3 / 2
0.1.8 3 / 2
0.1.7 3 / 2
0.1.6 3 / 2
0.1.5 3 / 2
0.1.4 3 / 2
0.1.3 3 / 2
0.1.2 3 / 2
0.1.1 3 / 2
0.1.0 3 / 2

v0.1.5

1 finding
INFO No provenance attestation provenance

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

v0.1.4

1 finding
INFO No provenance attestation provenance

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

v0.1.3

1 finding
INFO No provenance attestation provenance

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

v0.1.2

1 finding
INFO No provenance attestation provenance

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

v0.1.1

1 finding
INFO No provenance attestation provenance

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

v0.1.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.