← Home

@typescript/vfs

npm Repository Homepage
3
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

microsoft1estypescript-botweswighamandrewbranchtypescript-deploysjakebailey

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package under @typescript namespace from the official Microsoft TypeScript team; Levenshtein match against 'qs' is purely coincidental and not a typosquat. ai
provenance no-provenance AI (provenance): Established Microsoft/TypeScript team package with long history; lack of Sigstore provenance is common and not a risk signal for this publisher. ai

Versions (showing 3 of 3)

Version Deps Published
1.6.4 1 / 10
1.6.3 1 / 10
1.6.2 1 / 10

v1.6.4

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

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.

v1.6.2

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.