@everstake/wallet-sdk
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bs58 | AI (phantom-deps): Blockchain utility library; properly declared dependency for wallet SDK. | ai | |
| phantom-deps | phantom-dep:aptos | AI (phantom-deps): Core blockchain chain support; declared and used by SDK. | ai | |
| phantom-deps | phantom-dep:bip39 | AI (phantom-deps): BIP39 mnemonic support; standard for wallet SDKs. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): Cryptographic hashing; core wallet SDK dependency. | ai | |
| phantom-deps | phantom-dep:@mysten/sui.js | AI (phantom-deps): Sui blockchain chain support; declared dependency. | ai | |
| phantom-deps | phantom-dep:@cosmjs/stargate | AI (phantom-deps): Cosmos chain support; declared dependency for multi-chain SDK. | ai | |
| source-diff | encoded-string-file:src/ethereum/__fixtures__/index.ts | AI (source-diff): Hex ABI test fixture data, not a hidden payload. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-traffic SDK with consistent long-term maintainer; not a takeover indicator. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.0.15 | 5 / 14 | |
| 1.0.14 | 5 / 14 | |
| 1.0.13 | 5 / 14 | |
| 1.0.12 | 5 / 14 | |
| 1.0.11 | 5 / 14 | |
| 1.0.10 | 5 / 14 | |
| 1.0.9 | 5 / 14 | |
| 1.0.7 | 4 / 14 | |
| 1.0.5 | 4 / 14 | |
| 1.0.4 | 4 / 14 | |
| 1.0.1 | 11 / 14 | |
| 1.0.0 | 11 / 14 |
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.