@drifted/qa
this is sort of meant to be like test helpers that are default in rails. just stuff I normally use that allows me to test quickly.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small internal test-helper package; lack of Sigstore provenance is not a disqualifier here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private/internal scoped package; sparse metadata is expected, not indicative of spam or malice. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic requires use path.join(__dirname, ...) with string literals to load local files — not user-controlled input. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @drifted/qa is a personal test-helper library, not a typosquat of qs. | ai | |
| phantom-deps | phantom-dep:handlebars | AI (phantom-deps): Handlebars declared as dependency and referenced in config; phantom-dep heuristic misfires here. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): 2-edit distance from koa is coincidental; package is clearly a scoped test utility. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): 2-edit distance from pg is coincidental; package is clearly a scoped test utility. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.0.33 | 8 / 2 | |
| 0.0.32 | 8 / 2 | |
| 0.0.16 | 8 / 2 | |
| 0.0.14 | 8 / 2 | |
| 0.0.11 | 8 / 1 | |
| 0.0.10 | 8 / 1 | |
| 0.0.6 | 8 / 1 | |
| 0.0.5 | 8 / 1 | |
| 0.0.2 | 8 / 1 | |
| 0.0.1 | 8 / 1 |
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.