@tronweb3/tronwallet-adapter-bitkeep
Wallet adapter for Bitget(BitKeep) Wallet extension and app.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/umd/index.js | AI (source-diff): UMD bundler output from new build:umd script, not true obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from added UMD bundle files, expected given new build target. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adds official @bitget-wallet SDK matching package's stated Bitget wallet adapter purpose. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-wide maintainer transition across many sibling packages with clean track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with same org-wide transition, no code changes accompany it. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is common and not a risk indicator here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 2 / 3 | |
| 1.1.8 | 2 / 3 | |
| 1.1.7 | 2 / 3 | |
| 1.1.6 | 2 / 3 | |
| 1.1.5 | 2 / 3 | |
| 1.1.4 | 3 / 3 | |
| 1.1.2 | 3 / 3 | |
| 1.1.1 | 3 / 3 | |
| 1.1.0 | 3 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 3 |
v1.1.4
2 findingsThis version was published by a different npm account than previous versions on 2025-03-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.