← Home

@jjlmoya/utils-cooking

npm
11
Versions
—
License
Yes
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

jjlmoya

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:astro AI (phantom-deps): Astro framework dep used via config/CLI, not direct import — expected pattern. ai
phantom-deps phantom-dep:astro-icon AI (phantom-deps): Astro plugin referenced in astro config, not direct import. ai
phantom-deps phantom-dep:@iconify-json/mdi AI (phantom-deps): Icon JSON set consumed by astro-icon plugin, not directly imported. ai
bogus-package bogus-package AI (bogus-package): Personal scoped utility package; missing metadata is consistent with author's publishing style across 23 versions. ai
npm-metadata no-description AI (npm-metadata): Stable pattern for this publisher's scoped packages; not a malice indicator. ai

Versions (showing 11 of 11)

Version Deps Published
1.12.0 4 / 14
1.11.0 4 / 14
1.10.0 4 / 14
1.9.0 4 / 14
1.8.0 4 / 14
1.7.0 4 / 14
1.6.0 4 / 14
1.5.0 4 / 14
1.4.0 4 / 14
1.3.0 4 / 14
1.2.0 4 / 14

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

1 finding
LOW No provenance attestation provenance

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

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

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

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