@1delta/margin-fetcher
Multi-protocol lending data fetcher supporting Morpho Blue, Aave V2/V3, Compound V2/V3, Euler, Init, and Lista DAO. Provides public market data (rates, TVL, configs) and per-user position data (balances, shares, collateral) in a unified format.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:async-retry | AI (phantom-deps): async-retry is a declared runtime dependency; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @1delta/* packages; publisher has clean track record. | ai |
Versions (showing 100 of 170)
| Version | Deps | Published |
|---|---|---|
| 0.0.2889 | 9 / 5 | |
| 0.0.337 | 9 / 5 | |
| 0.0.336 | 9 / 5 | |
| 0.0.335 | 9 / 5 | |
| 0.0.334 | 9 / 5 | |
| 0.0.333 | 9 / 5 | |
| 0.0.332 | 9 / 5 | |
| 0.0.331 | 9 / 5 | |
| 0.0.330 | 9 / 5 | |
| 0.0.329 | 9 / 5 | |
| 0.0.328 | 9 / 5 | |
| 0.0.327 | 9 / 5 | |
| 0.0.325 | 9 / 5 | |
| 0.0.324 | 9 / 5 | |
| 0.0.323 | 9 / 5 | |
| 0.0.322 | 9 / 5 | |
| 0.0.321 | 9 / 5 | |
| 0.0.320 | 9 / 5 | |
| 0.0.319 | 9 / 5 | |
| 0.0.318 | 9 / 5 | |
| 0.0.317 | 9 / 5 | |
| 0.0.316 | 9 / 5 | |
| 0.0.314 | 9 / 5 | |
| 0.0.313 | 9 / 5 | |
| 0.0.312 | 9 / 5 | |
| 0.0.311 | 9 / 5 | |
| 0.0.310 | 9 / 5 | |
| 0.0.309 | 9 / 5 | |
| 0.0.308 | 9 / 5 | |
| 0.0.307 | 9 / 5 | |
| 0.0.306 | 9 / 5 | |
| 0.0.305 | 9 / 5 | |
| 0.0.304 | 9 / 5 | |
| 0.0.303 | 9 / 5 | |
| 0.0.302 | 9 / 5 | |
| 0.0.300 | 9 / 5 | |
| 0.0.288 | 9 / 5 | |
| 0.0.286 | 9 / 5 | |
| 0.0.285 | 8 / 5 | |
| 0.0.284 | 8 / 5 | |
| 0.0.283 | 8 / 5 | |
| 0.0.282 | 8 / 5 | |
| 0.0.281 | 8 / 5 | |
| 0.0.280 | 8 / 5 | |
| 0.0.279 | 8 / 5 | |
| 0.0.278 | 8 / 5 | |
| 0.0.277 | 8 / 5 | |
| 0.0.276 | 8 / 5 | |
| 0.0.275 | 8 / 5 | |
| 0.0.274 | 8 / 5 | |
| 0.0.273 | 8 / 5 | |
| 0.0.272 | 8 / 5 | |
| 0.0.271 | 8 / 5 | |
| 0.0.270 | 8 / 5 | |
| 0.0.269 | 8 / 5 | |
| 0.0.268 | 8 / 5 | |
| 0.0.267 | 8 / 5 | |
| 0.0.266 | 8 / 5 | |
| 0.0.265 | 8 / 5 | |
| 0.0.263 | 8 / 5 | |
| 0.0.262 | 8 / 5 | |
| 0.0.261 | 8 / 5 | |
| 0.0.258 | 8 / 5 | |
| 0.0.254 | 8 / 5 | |
| 0.0.252 | 8 / 5 | |
| 0.0.247 | 7 / 5 | |
| 0.0.237 | 7 / 5 | |
| 0.0.236 | 7 / 5 | |
| 0.0.235 | 7 / 5 | |
| 0.0.234 | 7 / 5 | |
| 0.0.233 | 7 / 5 | |
| 0.0.232 | 7 / 5 | |
| 0.0.231 | 7 / 5 | |
| 0.0.230 | 7 / 5 | |
| 0.0.229 | 7 / 5 | |
| 0.0.228 | 7 / 5 | |
| 0.0.224 | 7 / 5 | |
| 0.0.223 | 7 / 5 | |
| 0.0.222 | 7 / 5 | |
| 0.0.221 | 7 / 5 | |
| 0.0.220 | 7 / 5 | |
| 0.0.219 | 7 / 5 | |
| 0.0.218 | 7 / 5 | |
| 0.0.217 | 7 / 5 | |
| 0.0.216 | 7 / 5 | |
| 0.0.215 | 7 / 5 | |
| 0.0.214 | 7 / 5 | |
| 0.0.213 | 7 / 5 | |
| 0.0.212 | 7 / 5 | |
| 0.0.211 | 7 / 5 | |
| 0.0.210 | 7 / 5 | |
| 0.0.209 | 7 / 5 | |
| 0.0.207 | 7 / 5 | |
| 0.0.206 | 7 / 5 | |
| 0.0.205 | 7 / 5 | |
| 0.0.204 | 7 / 5 | |
| 0.0.203 | 7 / 5 | |
| 0.0.202 | 7 / 5 | |
| 0.0.200 | 7 / 5 | |
| 0.0.199 | 7 / 5 |
v0.0.337
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.336
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.335
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.334
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.333
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.332
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.331
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.330
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.329
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.328
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.327
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.325
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.324
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.323
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.322
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.321
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.320
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.319
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.318
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.317
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.316
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.314
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.313
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.312
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.311
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.310
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.309
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.308
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.218
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.217
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.216
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.215
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.214
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.213
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.212
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.211
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.210
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.209
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.207
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.206
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.205
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.204
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.203
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.202
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.200
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.199
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.