@desplega.ai/qa-use
QA automation tool for browser testing with MCP server support
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/src/cli/generated/docs-content.d.ts | AI (source-diff): Long lines are auto-generated markdown documentation embedded in a TS declaration file, not obfuscated code. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 44 versions; publisher has clean track record, no provenance is common for this org. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Fires in test file asserting localhost URL detection logic; not a real outbound request. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 2.19.0 | 10 / 13 | |
| 2.18.0 | 10 / 13 | |
| 2.17.0 | 10 / 13 | |
| 2.16.0 | 10 / 13 | |
| 2.15.4 | 10 / 13 | |
| 2.15.3 | 10 / 13 | |
| 2.15.2 | 10 / 13 | |
| 2.15.1 | 10 / 13 | |
| 2.15.0 | 10 / 13 | |
| 2.14.1 | 10 / 13 | |
| 2.14.0 | 10 / 13 | |
| 2.13.2 | 10 / 13 | |
| 2.13.1 | 10 / 13 | |
| 2.11.0 | 10 / 13 | |
| 2.10.1 | 10 / 13 | |
| 2.9.0 | 10 / 13 | |
| 2.8.7 | 10 / 13 | |
| 2.8.6 | 10 / 13 | |
| 2.8.4 | 10 / 13 | |
| 2.8.2 | 10 / 13 | |
| 2.8.1 | 10 / 13 | |
| 2.8.0 | 10 / 13 | |
| 2.7.1 | 10 / 13 | |
| 2.7.0 | 10 / 13 | |
| 2.6.1 | 10 / 13 | |
| 2.5.4 | 10 / 13 | |
| 2.5.3 | 10 / 13 | |
| 2.5.2 | 10 / 13 | |
| 2.5.1 | 10 / 13 | |
| 2.5.0 | 10 / 13 | |
| 2.4.2 | 10 / 19 | |
| 2.4.1 | 10 / 19 | |
| 2.4.0 | 10 / 19 | |
| 2.3.4 | 10 / 19 | |
| 2.3.3 | 10 / 19 | |
| 2.3.2 | 10 / 19 | |
| 2.3.1 | 10 / 19 | |
| 2.3.0 | 10 / 19 | |
| 2.2.5 | 10 / 19 | |
| 2.2.4 | 10 / 19 | |
| 2.2.3 | 10 / 19 | |
| 2.2.2 | 10 / 19 | |
| 2.1.7 | 9 / 19 | |
| 2.1.5 | 9 / 19 | |
| 2.1.3 | 9 / 19 | |
| 2.1.2 | 9 / 19 | |
| 2.1.1 | 9 / 19 | |
| 2.1.0 | 9 / 19 | |
| 2.0.1 | 9 / 19 |
v2.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.