← Home

@ch1c0t/ext

npm

JavaScript amenities

21
Versions
0BSD
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

ch1c0t

Keywords

coffeescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:next AI (typosquat): Scoped package @ch1c0t/ext; not impersonating 'next'. Levenshtein match is coincidental. ai
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped package under author's own namespace; not impersonating 'nuxt'. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped package under author's own namespace; not impersonating 'jest'. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped package under author's own namespace; not impersonating 'got'. ai

Versions (showing 21 of 21)

Version Deps Published
0.4.0 8 / 2
0.3.3 8 / 2
0.3.2 7 / 2
0.2.5 6 / 2
0.2.4 6 / 2
0.2.3 5 / 2
0.2.2 5 / 2
0.2.1 4 / 2
0.2.0 3 / 2
0.1.3 3 / 2
0.1.2 3 / 2
0.1.1 2 / 2
0.1.0 2 / 2
0.0.8 2 / 2
0.0.7 2 / 2
0.0.6 2 / 2
0.0.5 2 / 2
0.0.4 2 / 2
0.0.3 2 / 2
0.0.2 2 / 2
0.0.1 2 / 2

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

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