@webability/cli
Abilyo by WebAbility — WCAG accessibility scanner for your terminal
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ora | AI (phantom-deps): CLI is bundled via tsup; declared deps are bundled into dist/, not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:conf | AI (phantom-deps): Bundled via tsup; declared dep consumed at build time. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Bundled via tsup; declared dep consumed at build time. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Bundled via tsup; declared dep consumed at build time. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Declared runtime dep; likely used via workspace package or config files not directly analyzed. | ai | |
| phantom-deps | phantom-dep:playwright | AI (phantom-deps): Declared runtime dep for browser automation in accessibility scanning; workspace monorepo may obscure direct imports. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped accessibility CLI package; name similarity to 'joi' is coincidental, not impersonation. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.2 | 7 / 4 | |
| 1.1.1 | 7 / 4 | |
| 1.1.0 | 7 / 4 | |
| 1.0.1 | 7 / 4 | |
| 1.0.0 | 7 / 4 |
v1.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webabilityio.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.