@howells/ai
Unified AI client for all projects — Gateway, OpenRouter, direct providers, tiered language models, and retrieval models.
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): Personal scoped package; no provenance CI setup; consistent across all versions. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package @howells/ai; edit-distance match to 'hapi' is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @howells/ai; edit-distance match to 'pg' is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @howells/ai; edit-distance match to 'qs' is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @howells/ai; edit-distance match to 'joi' is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @howells/ai; edit-distance match to 'ajv' is coincidental, not impersonation. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.1.20 | 10 / 4 | |
| 0.1.18 | 8 / 3 | |
| 0.1.17 | 8 / 3 | |
| 0.1.16 | 8 / 3 | |
| 0.1.15 | 8 / 3 | |
| 0.1.14 | 8 / 3 | |
| 0.1.13 | 8 / 3 | |
| 0.1.12 | 8 / 3 | |
| 0.1.11 | 8 / 3 | |
| 0.1.10 | 8 / 3 | |
| 0.1.9 | 8 / 3 | |
| 0.1.8 | 8 / 3 |
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.