@vechain/dapp-kit
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:events | AI (phantom-deps): Build config reference in dual-module package; not a real import gap. | ai | |
| phantom-deps | phantom-dep:valtio | AI (phantom-deps): Build config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vechain/sdk-errors | AI (phantom-deps): Same org scope; likely re-exported or type-only usage in build config. | ai | |
| phantom-deps | phantom-dep:@walletconnect/modal | AI (phantom-deps): Build config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@walletconnect/utils | AI (phantom-deps): Build config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@vechain/connex-wallet-buddy | AI (phantom-deps): Same org scope; phantom heuristic fires on config-level reference. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 10 / 11 | |
| 2.1.2 | 10 / 11 | |
| 2.0.4 | 8 / 11 | |
| 2.0.3 | 8 / 11 | |
| 2.0.2 | 8 / 11 | |
| 2.0.1 | 8 / 11 |
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.