@terreno/ai
AI service layer for Terreno apps - GPT chat, request logging, and admin tools.
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 @terreno/ai; not a typosquat of hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @terreno/ai; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @terreno/ai; not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @terreno/ai; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @terreno/ai; not a typosquat of ajv. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): @opentelemetry/api is declared in dependencies and used via OTel SDK; phantom-dep heuristic false positive. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.17.0 | 10 / 13 | |
| 0.16.1 | 9 / 13 | |
| 0.15.2 | 9 / 13 | |
| 0.15.1 | 9 / 13 | |
| 0.15.0 | 9 / 13 | |
| 0.14.2 | 9 / 13 | |
| 0.14.1 | 9 / 13 | |
| 0.14.0 | 9 / 13 | |
| 0.13.3 | 8 / 13 | |
| 0.13.1 | 8 / 13 | |
| 0.13.0 | 8 / 13 | |
| 0.12.2 | 8 / 13 | |
| 0.12.1 | 8 / 13 | |
| 0.12.0 | 8 / 13 | |
| 0.11.9 | 8 / 13 | |
| 0.11.8 | 8 / 13 | |
| 0.11.7 | 8 / 13 | |
| 0.11.6 | 8 / 13 | |
| 0.11.5 | 8 / 13 | |
| 0.11.3 | 9 / 11 | |
| 0.11.2 | 9 / 11 | |
| 0.11.1 | 9 / 11 | |
| 0.11.0 | 9 / 11 | |
| 0.10.0 | 9 / 11 | |
| 0.9.3 | 9 / 11 | |
| 0.9.2 | 9 / 11 | |
| 0.9.1 | 9 / 11 | |
| 0.9.0 | 9 / 11 | |
| 0.8.3 | 9 / 11 | |
| 0.8.2 | 9 / 11 | |
| 0.8.1 | 9 / 11 | |
| 0.8.0 | 9 / 11 | |
| 0.7.2 | 10 / 11 | |
| 0.7.1 | 10 / 11 | |
| 0.7.0 | 10 / 11 | |
| 0.6.0 | 5 / 10 | |
| 0.5.0 | 5 / 10 | |
| 0.4.2 | 5 / 10 | |
| 0.3.2 | 5 / 10 |
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.