@patternfly/chatbot
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:rehype-unwrap-images | AI (dependencies): rehype-unwrap-images is a standard unified/rehype ecosystem plugin; expected dependency for markdown rendering. | ai | |
| dependencies | unvetted-dep:rehype-external-links | AI (dependencies): rehype-external-links is a standard unified/rehype ecosystem plugin; expected dependency for markdown rendering. | ai | |
| dependencies | unvetted-dep:@segment/analytics-next | AI (dependencies): Segment analytics is a well-known analytics SDK; its use in a chatbot UI library is expected. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
v6.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dlabaj) than the most recent previously approved version (ausuliv) on 2026-05-21, but dlabaj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.