qap
1
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
rootslab
Keywords
parserfastqapparsequick searchpattern matchingpatternstringsearch
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): qap is a distinct parser library, not a typosquat of hapi; 2-edit Levenshtein distance is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): qap is a distinct parser library, not a typosquat of qs; 2-edit Levenshtein distance is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): qap is a distinct parser library, not a typosquat of yup; 2-edit Levenshtein distance is coincidental. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 0 / 0 |
v3.3.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.