thirdweb
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/scripts/bridge-widget.js | AI (source-diff): Long strings are minified/bundled JS (viem error classes visible); standard build artifact for this SDK. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 4779 versions and publishes continuously; dormancy signal is a false positive. | ai | |
| dependencies | unvetted-dep:@thirdweb-dev/engine | AI (dependencies): First-party thirdweb dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@thirdweb-dev/insight | AI (dependencies): First-party thirdweb dependency; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is consistent across all prior versions. | ai |
v5.120.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (thirdweb-bot) than the most recent previously approved version (joaquim-verges) on 2026-06-10, but thirdweb-bot 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.
v5.120.0
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.119.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.