@ooneex/ai
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 @ooneex/ai; no meaningful similarity to hapi. Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @ooneex/ai; no meaningful similarity to pg. Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @ooneex/ai; no meaningful similarity to qs. Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @ooneex/ai; no meaningful similarity to joi. Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @ooneex/ai; no meaningful similarity to ajv. Levenshtein match is spurious. | ai | |
| phantom-deps | phantom-dep:@ooneex/http-status | AI (phantom-deps): @ooneex/http-status is declared as a runtime dep; may be re-exported or used indirectly. Same org scope, stable false positive. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 1 / 0 | |
| 1.2.2 | 7 / 1 | |
| 1.2.1 | 7 / 1 | |
| 1.2.0 | 7 / 1 | |
| 1.1.14 | 12 / 1 | |
| 1.1.13 | 12 / 1 | |
| 1.1.12 | 12 / 1 | |
| 1.1.11 | 12 / 1 | |
| 1.1.10 | 12 / 1 | |
| 1.1.9 | 12 / 1 | |
| 1.1.7 | 12 / 1 | |
| 1.1.6 | 11 / 1 | |
| 1.1.5 | 11 / 1 | |
| 1.1.4 | 11 / 1 | |
| 1.1.2 | 11 / 1 | |
| 1.1.1 | 11 / 1 | |
| 1.1.0 | 11 / 1 | |
| 1.0.2 | 11 / 1 | |
| 1.0.1 | 10 / 1 | |
| 1.0.0 | 10 / 1 | |
| 0.0.18 | 9 / 1 | |
| 0.0.17 | 9 / 1 | |
| 0.0.16 | 9 / 1 | |
| 0.0.15 | 9 / 1 | |
| 0.0.14 | 9 / 1 | |
| 0.0.13 | 9 / 1 | |
| 0.0.12 | 9 / 1 | |
| 0.0.11 | 9 / 1 | |
| 0.0.10 | 9 / 1 | |
| 0.0.9 | 9 / 1 | |
| 0.0.8 | 9 / 1 | |
| 0.0.7 | 9 / 1 | |
| 0.0.6 | 9 / 1 | |
| 0.0.5 | 9 / 1 | |
| 0.0.4 | 9 / 1 |
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
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.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
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.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.