← Home

@atcute/cid

npm Repository
14
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

externdefs

Keywords

atprotociddasl

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped @atcute package; Levenshtein match to uuid is coincidental, not a squatting attempt. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped @atcute package; Levenshtein match to zod is coincidental, not a squatting attempt. ai

Versions (showing 14 of 14)

Version Deps Published
2.4.2 2 / 2
2.4.1 2 / 2
2.4.0 2 / 2
2.3.0 2 / 2
2.2.6 2 / 1
2.2.5 2 / 1
2.2.4 2 / 1
2.2.3 2 / 1
2.2.2 2 / 1
2.2.1 2 / 1
2.2.0 2 / 1
2.1.0 3 / 1
2.0.1 2 / 1
2.0.0 2 / 1

v2.4.2

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.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.

v2.0.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.