@types/q
2
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
types
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @types/q is the official TypeScript definitions for the 'q' promise library, not a typosquat of 'qs'. The short name causes false Levenshtein matches; this is stable for all versions. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @types/q is the official TypeScript definitions for the 'q' promise library, not a typosquat of 'pg'. False positive due to short package name; stable for all versions. | ai | |
| provenance | no-provenance | AI (provenance): DefinitelyTyped @types packages predate Sigstore provenance; absence is expected and not a risk signal for this publisher. | ai |
v1.5.8
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'qs'
typosquat
Package name '@types/q' is 1 edit(s) away from popular package 'qs'.
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.5.2
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'qs'
typosquat
Package name '@types/q' is 1 edit(s) away from popular package 'qs'.
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.