@gemini-wallet/core
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Standard CJS bundler output from Bun build; not obfuscated. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from adding bundled CJS dist output; normal for build config change. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): EVM contract bytecode from viem bundled in dist; standard for wallet SDK packages. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Gemini wallet SDK; name similarity to 'cors' is coincidental, not impersonation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard cross-environment base64 utility; no obfuscation or payload hiding. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 2 / 19 | |
| 0.3.1 | 2 / 23 | |
| 0.3.0 | 2 / 4 | |
| 0.2.0 | 2 / 14 | |
| 0.1.1 | 2 / 14 | |
| 0.1.0 | 2 / 14 | |
| 0.0.1 | 2 / 6 |
v0.3.2
2 findingsPackage name '@gemini-wallet/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Modified 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.
v0.2.0
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.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.