← Home

@scalprum/core

npm Repository Homepage
9
Versions
—
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

hyperkidkarelhalachmulder

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA attestation; this is the expected pattern for automated releases. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer added alongside CI migration; consistent with legitimate org transition for this established package. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @scalprum/core is a scoped package in the scalprum namespace, not a typosquat of cors; Levenshtein match is coincidental. ai

Versions (showing 9 of 9)

Version Deps Published
0.10.1 2 / 0
0.10.0 2 / 0
0.9.3 2 / 0
0.9.2 2 / 0
0.9.0 2 / 0
0.8.3 2 / 0
0.8.2 2 / 0
0.8.1 2 / 0
0.8.0 2 / 0

v0.10.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.8.3

1 finding
LOW No provenance attestation provenance

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

v0.8.2

1 finding
LOW No provenance attestation provenance

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

v0.8.1

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