@webneat/ai
A TypeScript library for building AI agents with event-driven observability and functional state management
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 @webneat/ai; no resemblance to hapi beyond edit distance. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @webneat/ai; no resemblance to pg beyond edit distance. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @webneat/ai; no resemblance to qs beyond edit distance. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @webneat/ai; no resemblance to joi beyond edit distance. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @webneat/ai; no resemblance to ajv beyond edit distance. | ai | |
| phantom-deps | phantom-dep:msw | AI (phantom-deps): msw is a mock service worker used for testing/mocking HTTP; plausible as a runtime dep for AI SDK mocking. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.12 | 3 / 2 | |
| 0.0.10 | 3 / 3 | |
| 0.0.9 | 3 / 3 | |
| 0.0.8 | 3 / 1 | |
| 0.0.5 | 3 / 1 | |
| 0.0.4 | 3 / 1 | |
| 0.0.3 | 4 / 0 | |
| 0.0.2 | 4 / 4 | |
| 0.0.1 | 4 / 11 |
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.