← Home

@types/jsesc

4
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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:jest AI (typosquat): @types/jsesc is a legitimate DefinitelyTyped package for the jsesc library; the Levenshtein match to 'jest' is a false positive — unrelated packages with different purposes. ai
provenance no-provenance AI (provenance): DefinitelyTyped packages published via the 'types' npm account do not include Sigstore provenance; this is expected and stable for all @types/* packages. ai

Versions (showing 4 of 4)

Version Deps Published
3.0.3 0 / 0
3.0.2 0 / 0
3.0.1 0 / 0
3.0.0 0 / 0

v3.0.2

1 finding
INFO No provenance attestation provenance

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

v3.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.