@reown/appkit
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): semver is a well-established, widely-trusted package; addition is benign for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Reown org manages this package; single maintainer removal without suspicious additions in a large, active org is routine. | ai | |
| phantom-deps | phantom-dep:valtio | AI (phantom-deps): valtio is a legitimate runtime dependency of the appkit ecosystem; phantom-dep fires because it may be re-exported rather than directly imported at the top level. | ai | |
| phantom-deps | phantom-dep:@reown/appkit-polyfills | AI (phantom-deps): Same-org sibling package legitimately listed as a runtime dependency; phantom-dep is a stable false positive for this aggregator package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs a version compatibility check script (appkit-version-check.js) — a standard monorepo pattern for @reown/appkit to verify sibling package version consistency. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.8.20 | 13 / 12 | |
| 1.8.19 | 13 / 12 | |
| 1.8.18 | 13 / 12 | |
| 1.8.17 | 13 / 12 | |
| 1.8.16 | 13 / 12 | |
| 1.8.15 | 13 / 12 | |
| 1.8.14 | 13 / 12 | |
| 1.8.13 | 13 / 12 | |
| 1.8.3 | 13 / 12 | |
| 1.8.2 | 13 / 12 | |
| 1.8.1 | 13 / 12 | |
| 1.8.0 | 13 / 12 | |
| 1.7.18 | 13 / 12 | |
| 1.7.16 | 14 / 10 | |
| 1.7.14 | 14 / 12 | |
| 1.7.11 | 14 / 12 | |
| 1.7.10 | 13 / 12 | |
| 1.7.9 | 13 / 12 | |
| 1.7.8 | 13 / 12 | |
| 1.7.7 | 13 / 12 | |
| 1.7.6 | 13 / 12 | |
| 1.7.5 | 13 / 12 | |
| 1.7.4 | 13 / 12 |
v1.8.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.19
2 findingsScript: node scripts/appkit-version-check.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.