@metamask/test-dapp-stellar
A test dapp for Stellar MetaMask integration
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 | obfuscated-file:dist/assets/index-CcG8WOGt.js | AI (source-diff): Standard Vite/React production bundle; minification is expected for this test-dapp package. | ai | |
| source-diff | net-exec-file:dist/assets/index-CcG8WOGt.js | AI (source-diff): Network calls and dynamic patterns are from bundled React/WalletConnect code, not dropper behavior. | ai | |
| phantom-deps | phantom-dep:@metamask/connect-stellar | AI (phantom-deps): Same-org dep bundled via Vite; not directly imported in source but used transitively through the build. | ai | |
| phantom-deps | phantom-dep:@walletconnect/sign-client | AI (phantom-deps): Declared in lavamoat allowlist for security scanning; stable false positive. | ai | |
| phantom-deps | phantom-dep:depcheck | AI (phantom-deps): depcheck is a linting tool used in lint:dependencies script; stable false positive. | ai | |
| phantom-deps | phantom-dep:@creit.tech/stellar-wallets-kit | AI (phantom-deps): Declared in lavamoat allowlist for security scanning; stable false positive. | ai | |
| phantom-deps | phantom-dep:@reown/appkit | AI (phantom-deps): Declared in lavamoat allowlist for security scanning; stable false positive. | ai | |
| phantom-deps | phantom-dep:@walletconnect/types | AI (phantom-deps): Type dependency in lavamoat allowlist; stable false positive. | ai |
v0.2.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.