@keplr-wallet/background
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is confirmed by SLSA provenance attestation from the official chainapsis/keplr-wallet repo. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of fixed constants (e.g. '1b','1c') for Ethereum signature construction; not a malicious payload. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP (127.0.0.1) appears only in test files for phishing-list service spec; not production code. | ai | |
| phantom-deps | phantom-dep:delay | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/tx | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:ledger-bitcoin | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/common | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@keplr-wallet/popup | AI (phantom-deps): Same-org monorepo package; stable false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is routine in a crypto wallet for signing message payloads; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethersproject/wallet | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethersproject/address | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/hw-transport | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/hw-app-starknet | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@keplr-wallet/ledger-cosmos | AI (phantom-deps): Same-org monorepo package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/hw-transport-webhid | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/hw-transport-webusb | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/hw-app-eth | AI (phantom-deps): Monorepo build pattern; stable false positive. | ai |
Versions (showing 47 of 247)
| Version | Deps | Published |
|---|---|---|
| 0.12.147 | 33 / 5 | |
| 0.12.146 | 33 / 5 | |
| 0.12.145 | 33 / 5 | |
| 0.12.144 | 33 / 5 | |
| 0.12.143 | 33 / 5 | |
| 0.12.142 | 33 / 5 | |
| 0.12.141 | 33 / 5 | |
| 0.12.140 | 33 / 5 | |
| 0.12.139 | 33 / 5 | |
| 0.12.138 | 33 / 5 | |
| 0.12.137 | 33 / 5 | |
| 0.12.136 | 33 / 5 | |
| 0.12.135 | 33 / 5 | |
| 0.12.133 | 33 / 5 | |
| 0.12.132 | 33 / 5 | |
| 0.12.131 | 33 / 5 | |
| 0.12.130 | 33 / 5 | |
| 0.12.129 | 33 / 5 | |
| 0.12.128 | 33 / 5 | |
| 0.12.127 | 33 / 5 | |
| 0.12.126 | 33 / 5 | |
| 0.12.125 | 33 / 5 | |
| 0.12.124 | 33 / 5 | |
| 0.12.123 | 33 / 5 | |
| 0.12.122 | 33 / 5 | |
| 0.12.121 | 33 / 5 | |
| 0.12.120 | 33 / 5 | |
| 0.12.119 | 33 / 5 | |
| 0.12.118 | 33 / 5 | |
| 0.12.117 | 33 / 5 | |
| 0.12.116 | 33 / 5 | |
| 0.12.115 | 33 / 5 | |
| 0.12.114 | 33 / 5 | |
| 0.12.113 | 33 / 5 | |
| 0.12.112 | 33 / 5 | |
| 0.12.111 | 33 / 5 | |
| 0.12.110 | 33 / 5 | |
| 0.12.109 | 33 / 5 | |
| 0.12.108 | 33 / 5 | |
| 0.12.107 | 33 / 5 | |
| 0.12.106 | 33 / 5 | |
| 0.12.105 | 33 / 5 | |
| 0.12.104 | 33 / 5 | |
| 0.12.103 | 33 / 5 | |
| 0.12.102 | 33 / 5 | |
| 0.12.101 | 33 / 5 | |
| 0.12.100 | 33 / 5 |
v0.12.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.141
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.