chat
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/chat-D9UYaaNO.d.ts | AI (source-diff): Bundled .d.ts type declaration file with long lines; not obfuscated. Stable for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Vercel uses GitHub Actions / vercel-release-bot for automated npm publishing; this is the expected publisher for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): vercel-release-bot is Vercel's standard release automation account; stable for this package. | ai | |
| dependencies | unvetted-dep:mdast-util-to-string | AI (dependencies): mdast-util-to-string is a well-known, widely-used package in the unified/remark ecosystem; no security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with strong publisher track record; lack of provenance attestation is a hygiene note, not a security risk. | ai | |
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): chat is a long-established Vercel package for chat platform abstraction; the levenshtein match to chalk is coincidental with no impersonation intent. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.29.0 | 7 / 7 | |
| 4.28.1 | 7 / 5 | |
| 4.27.0 | 7 / 5 | |
| 4.26.0 | 7 / 5 | |
| 4.25.0 | 7 / 5 | |
| 4.23.0 | 7 / 5 | |
| 4.20.2 | 7 / 5 | |
| 4.15.0 | 6 / 5 | |
| 4.13.0 | 6 / 5 | |
| 4.4.1 | 6 / 5 | |
| 4.4.0 | 5 / 5 | |
| 4.3.0 | 5 / 5 | |
| 4.1.0 | 5 / 5 | |
| 4.0.2 | 5 / 5 | |
| 4.0.1 | 5 / 5 | |
| 4.0.0 | 5 / 5 |
v4.29.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.28.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.27.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.