@keplr-wallet/hooks
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): Chainapsis monorepo migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is consistent across all keplr-wallet packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethersproject/address | AI (phantom-deps): Likely used transitively or in type-only imports; stable false positive for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode is standard ETH address normalization (0x-prefix strip + lowercase + hex decode → Bech32); not malicious. | ai | |
| phantom-deps | phantom-dep:long | AI (phantom-deps): Protobuf-related dep used via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@keplr-wallet/background | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@keplr-wallet/crypto | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package. | ai |
Versions (showing 60 of 260)
| Version | Deps | Published |
|---|---|---|
| 0.12.148 | 16 / 0 | |
| 0.12.147 | 16 / 0 | |
| 0.12.146 | 16 / 0 | |
| 0.12.145 | 16 / 0 | |
| 0.12.144 | 16 / 0 | |
| 0.12.143 | 16 / 0 | |
| 0.12.142 | 16 / 0 | |
| 0.12.141 | 16 / 0 | |
| 0.12.140 | 16 / 0 | |
| 0.12.139 | 16 / 0 | |
| 0.12.138 | 16 / 0 | |
| 0.12.137 | 16 / 0 | |
| 0.12.136 | 16 / 0 | |
| 0.12.135 | 16 / 0 | |
| 0.12.133 | 16 / 0 | |
| 0.12.132 | 16 / 0 | |
| 0.12.131 | 16 / 0 | |
| 0.12.130 | 16 / 0 | |
| 0.12.129 | 16 / 0 | |
| 0.12.128 | 16 / 0 | |
| 0.12.127 | 16 / 0 | |
| 0.12.126 | 16 / 0 | |
| 0.12.125 | 16 / 0 | |
| 0.12.124 | 16 / 0 | |
| 0.12.123 | 16 / 0 | |
| 0.12.122 | 16 / 0 | |
| 0.12.121 | 16 / 0 | |
| 0.12.120 | 16 / 0 | |
| 0.12.119 | 16 / 0 | |
| 0.12.118 | 16 / 0 | |
| 0.12.117 | 16 / 0 | |
| 0.12.116 | 16 / 0 | |
| 0.12.115 | 16 / 0 | |
| 0.12.114 | 15 / 0 | |
| 0.12.113 | 15 / 0 | |
| 0.12.112 | 15 / 0 | |
| 0.12.111 | 15 / 0 | |
| 0.12.110 | 15 / 0 | |
| 0.12.109 | 15 / 0 | |
| 0.12.108 | 15 / 0 | |
| 0.12.107 | 15 / 0 | |
| 0.12.106 | 15 / 0 | |
| 0.12.105 | 15 / 0 | |
| 0.12.104 | 15 / 0 | |
| 0.12.103 | 15 / 0 | |
| 0.12.102 | 15 / 0 | |
| 0.12.101 | 15 / 0 | |
| 0.12.100 | 15 / 0 | |
| 0.12.98 | 15 / 0 | |
| 0.12.96 | 15 / 0 | |
| 0.12.95 | 15 / 0 | |
| 0.12.94 | 15 / 0 | |
| 0.12.91 | 15 / 0 | |
| 0.12.90 | 15 / 0 | |
| 0.12.89 | 15 / 0 | |
| 0.12.88 | 15 / 0 | |
| 0.12.87 | 15 / 0 | |
| 0.12.86 | 15 / 0 | |
| 0.12.85 | 15 / 0 | |
| 0.12.84 | 15 / 0 |
v0.12.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.12.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.