@tour-kit/ai
React AI chat widget with RAG & tour context — drop-in conversational assistant powered by Vercel AI SDK with vector search.
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 @tour-kit/ai package; Levenshtein match to 'hapi' is a coincidental substring hit, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @tour-kit/ai package; Levenshtein match to 'pg' is a coincidental substring hit, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @tour-kit/ai package; Levenshtein match to 'qs' is a coincidental substring hit, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @tour-kit/ai package; Levenshtein match to 'joi' is a coincidental substring hit, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @tour-kit/ai package; Levenshtein match to 'ajv' is a coincidental substring hit, not a typosquat. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 3 / 13 | |
| 0.11.5 | 3 / 13 | |
| 0.11.4 | 3 / 13 | |
| 0.11.3 | 3 / 13 | |
| 0.11.0 | 3 / 13 | |
| 0.10.0 | 3 / 13 | |
| 0.9.2 | 3 / 13 | |
| 0.9.1 | 3 / 13 | |
| 0.9.0 | 3 / 13 | |
| 0.8.0 | 3 / 13 | |
| 0.0.6 | 3 / 13 | |
| 0.0.5 | 5 / 14 | |
| 0.0.4 | 4 / 14 | |
| 0.0.3 | 4 / 14 | |
| 0.0.1 | 4 / 14 | |
| 0.0.0 | 3 / 14 |
v0.12.0
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.4
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.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.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. 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.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.
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.