@yeshwanthyk/ai
Unified LLM API with automatic model discovery and provider configuration
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped package under publisher's own namespace; not impersonating hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package under publisher's own namespace; not impersonating pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package under publisher's own namespace; not impersonating qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package under publisher's own namespace; not impersonating joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package under publisher's own namespace; not impersonating ajv. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Declared dependency used in build/config context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Declared dependency for schema conversion; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@mistralai/mistralai | AI (phantom-deps): Provider SDK dependency; stable false positive for this unified LLM wrapper package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.9 | 10 / 0 | |
| 0.2.8 | 10 / 0 | |
| 0.2.7 | 10 / 0 | |
| 0.2.6 | 10 / 0 | |
| 0.2.5 | 10 / 0 | |
| 0.1.6 | 10 / 0 | |
| 0.1.5 | 10 / 0 | |
| 0.1.4 | 10 / 0 | |
| 0.1.0 | 10 / 0 |
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.