@chat-adapter/whatsapp
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with Vercel org automation pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): vercel-release-bot and matt.straka are consistent with Vercel org ownership; legitimate maintainer addition. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 4.30.0 | 2 / 4 | |
| 4.29.0 | 2 / 4 | |
| 4.28.1 | 2 / 4 | |
| 4.27.0 | 2 / 4 | |
| 4.26.0 | 2 / 4 | |
| 4.25.0 | 2 / 4 | |
| 4.24.0 | 2 / 4 | |
| 4.23.0 | 2 / 4 | |
| 4.22.0 | 2 / 4 | |
| 4.21.0 | 2 / 4 | |
| 4.20.2 | 2 / 4 | |
| 4.20.1 | 2 / 4 | |
| 4.20.0 | 2 / 4 |
v4.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.29.0
1 findingPublished 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.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.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. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.