@blockrun/clawrouter
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Same viem EVM bytecode constants; stable false positive for this blockchain routing package. | ai | |
| source-diff | encoded-string-file:dist/cli.js | AI (source-diff): Long hex strings are EVM bytecode constants from viem library (deployless call, multicall3); not obfuscated payloads. | ai | |
| phantom-deps | phantom-dep:@x402/core | AI (phantom-deps): Part of the @x402 micropayment suite; referenced in config/plugin files. Stable false positive for this package's architecture. | ai | |
| phantom-deps | phantom-dep:@x402/fetch | AI (phantom-deps): Config-referenced dep for x402 payment protocol integration; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@solana/kit | AI (phantom-deps): Config-referenced dep for Solana payment support; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@scure/bip39 | AI (phantom-deps): Config-referenced cryptographic dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:viem | AI (phantom-deps): viem is an EVM library used in config/plugin context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@scure/bip32 | AI (phantom-deps): Config-referenced cryptographic dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@x402/evm | AI (phantom-deps): Deps are referenced in config/plugin files for dynamic loading in the openclaw plugin architecture; not a real phantom dep for this package. | ai | |
| phantom-deps | phantom-dep:@x402/svm | AI (phantom-deps): Same as @x402/evm — config-referenced dep for plugin architecture, stable false positive. | ai | |
| dependencies | unvetted-peer-dep:openclaw | AI (dependencies): openclaw is an optional peer dep from the same BlockRun ecosystem; it's also a devDependency, indicating intentional use. Stable false positive for this package. | ai |
Versions (showing 51 of 379)
| Version | Deps | Published |
|---|---|---|
| 0.12.203 | 8 / 9 | |
| 0.12.202 | 8 / 9 | |
| 0.12.201 | 8 / 9 | |
| 0.12.200 | 8 / 9 | |
| 0.12.199 | 8 / 9 | |
| 0.12.198 | 8 / 9 | |
| 0.12.197 | 8 / 9 | |
| 0.12.196 | 8 / 9 | |
| 0.12.195 | 8 / 9 | |
| 0.12.194 | 8 / 9 | |
| 0.12.193 | 8 / 9 | |
| 0.12.192 | 8 / 9 | |
| 0.12.191 | 8 / 9 | |
| 0.12.190 | 8 / 9 | |
| 0.12.189 | 8 / 9 | |
| 0.12.188 | 8 / 9 | |
| 0.12.187 | 8 / 9 | |
| 0.12.186 | 8 / 9 | |
| 0.12.185 | 8 / 9 | |
| 0.12.184 | 8 / 9 | |
| 0.12.183 | 8 / 9 | |
| 0.12.182 | 8 / 9 | |
| 0.12.181 | 8 / 9 | |
| 0.12.180 | 8 / 9 | |
| 0.12.179 | 8 / 9 | |
| 0.12.177 | 8 / 9 | |
| 0.12.176 | 8 / 9 | |
| 0.12.175 | 8 / 9 | |
| 0.12.174 | 8 / 9 | |
| 0.12.173 | 8 / 9 | |
| 0.12.172 | 8 / 9 | |
| 0.12.171 | 8 / 9 | |
| 0.12.169 | 8 / 9 | |
| 0.12.168 | 8 / 9 | |
| 0.12.167 | 8 / 9 | |
| 0.12.166 | 8 / 9 | |
| 0.12.165 | 8 / 9 | |
| 0.12.163 | 8 / 9 | |
| 0.12.162 | 8 / 9 | |
| 0.12.161 | 8 / 9 | |
| 0.12.160 | 8 / 9 | |
| 0.12.159 | 8 / 9 | |
| 0.12.158 | 8 / 9 | |
| 0.12.157 | 8 / 9 | |
| 0.12.156 | 8 / 9 | |
| 0.12.155 | 8 / 9 | |
| 0.12.154 | 8 / 9 | |
| 0.12.153 | 8 / 9 | |
| 0.12.152 | 8 / 9 | |
| 0.12.151 | 8 / 9 | |
| 0.12.150 | 8 / 9 |
v0.12.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.192
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.187
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 1bcmax.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.186
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 1bcmax.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.168
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.