← Home

@splendidlabz/utils

npm Homepage
17
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

zellwk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:marked AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. ai
phantom-deps phantom-dep:marked-mangle AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. ai
phantom-deps phantom-dep:marked-gfm-heading-id AI (phantom-deps): Declared runtime dep used via config/indirect import; stable false positive for this package. ai

Versions (showing 17 of 17)

Version Deps Published
1.13.0 9 / 5
1.12.1 9 / 6
1.12.0 11 / 6
1.11.6 11 / 6
1.11.2 11 / 6
1.11.1 11 / 6
1.10.6 11 / 6
1.9.1 11 / 6
1.9.0 9 / 6
1.8.2 9 / 6
1.8.1 9 / 6
1.7.0 9 / 7
1.6.0 9 / 5
1.5.1 9 / 5
1.5.0 4 / 4
1.4.0 4 / 4
1.3.0 4 / 4

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.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.