@prestyj/ai
Unified LLM streaming API for Anthropic and OpenAI
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped AI wrapper package; no resemblance to hapi in name or purpose. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped AI wrapper package; no resemblance to pg in name or purpose. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped AI wrapper package; no resemblance to qs in name or purpose. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped AI wrapper package; no resemblance to joi in name or purpose. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped AI wrapper package; no resemblance to ajv in name or purpose. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 3 / 2 | |
| 4.3.239 | 3 / 2 | |
| 4.3.238 | 3 / 2 | |
| 4.3.237 | 3 / 2 | |
| 4.3.210 | 3 / 2 | |
| 4.3.209 | 3 / 2 | |
| 4.3.207 | 3 / 2 | |
| 4.3.205 | 3 / 2 | |
| 4.3.201 | 3 / 2 | |
| 4.3.200 | 3 / 2 | |
| 4.3.164 | 3 / 2 | |
| 4.3.161 | 3 / 2 | |
| 4.3.160 | 3 / 2 | |
| 4.3.159 | 3 / 2 | |
| 4.3.96 | 3 / 2 | |
| 4.3.94 | 3 / 2 | |
| 4.3.85 | 3 / 2 | |
| 4.3.83 | 3 / 2 | |
| 4.3.59 | 3 / 2 | |
| 4.3.58 | 3 / 2 | |
| 4.3.57 | 3 / 2 | |
| 4.3.56 | 3 / 2 | |
| 4.3.55 | 3 / 2 | |
| 4.3.54 | 3 / 2 | |
| 4.3.34 | 3 / 2 | |
| 4.3.15 | 3 / 2 | |
| 4.2.77 | 3 / 2 | |
| 4.2.76 | 3 / 2 | |
| 4.2.75 | 3 / 2 | |
| 4.2.62 | 3 / 2 | |
| 4.2.56 | 3 / 2 | |
| 4.2.46 | 3 / 2 | |
| 4.2.45 | 3 / 2 | |
| 4.2.44 | 3 / 2 | |
| 4.2.16 | 3 / 2 | |
| 4.2.15 | 3 / 2 |
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.210
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.209
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.207
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.205
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.