@nan0web/ai
Unified AI Kernel for NaN0Web ecosystem - LLM provider abstraction
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 @nan0web/ai; no intent to impersonate hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @nan0web/ai; no intent to impersonate pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @nan0web/ai; no intent to impersonate qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @nan0web/ai; no intent to impersonate joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @nan0web/ai; no intent to impersonate ajv. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Deserializes float vector cache from hash,b64 CSV; benign data serialization pattern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 11 / 2 | |
| 3.1.0 | 11 / 2 | |
| 1.5.0 | 11 / 2 | |
| 1.4.2 | 11 / 2 | |
| 1.4.1 | 11 / 2 | |
| 1.4.0 | 10 / 3 | |
| 1.3.0 | 10 / 3 | |
| 1.2.1 | 9 / 3 | |
| 1.2.0 | 9 / 3 | |
| 1.1.0 | 5 / 3 | |
| 1.0.0 | 5 / 4 |
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.