Daily transfers, volume and coverage →
toolmint-pkg-trust.toolmint.workers.dev · toolmint-pkg-trust.toolmint.workers.dev · Dev & Code
Package trust pack: registry metadata + OSV vulns + typosquat neighbors (query: eco=npm|pypi&name=lodash)
The payout address is also published by 28 other service(s); the volume cannot be attributed to one of them.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-30) | — | — |
| Last 7 days | — | — |
| Last 30 days | — | — |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Receiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
| Network | Full wallet address | Evidence |
|---|---|---|
| Base | 0xfbf7413bcb3a604936775c96fdbe0b0c9c9e37f5 | Shared address · activity cannot be assigned to this serviceFrom source record · source: payai |
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
| With a measured call count | 931 (29.0 %) |
|---|---|
| With a published price | 1,151 (35.9 %) |
| With attributable inflows | 30 (0.9 %) |
| Observed inflows · 30d | $142.83 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
GitHub data. Repository stats, user profiles, and code-search results (stars, forks, language, topics, issues) via the GitHub REST API.
Call a read-only (view/pure) function on any deployed contract via eth_call and get the decoded result. Give the contract address and a human-readable signature (e.g. 'balanceOf(address) view returns (uint256)') plus arg...
Decode a vehicle VIN via the US NHTSA vPIC database: make, model, year, trim, body class, engine, fuel type, plant and vehicle type. Accepts full or partial VINs. Use it when an agent holds a VIN and needs the vehicle's...
Normalized NHTSA vPIC VIN decode (?vin=) — make/model/year/engine/body/… with fetch provenance, plus ORIGINAL factory new-vehicle warranty terms (basic/powertrain/corrosion/roadside/EV battery) keyed off make + model-yea...
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 0.005 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 5000 = 0.005 USDC per call on Base.
endpoint
https://toolmint-pkg-trust.toolmint.workers.dev/check
{
"type": "http",
"method": "GET",
"queryParams": {
"eco": "npm",
"name": "lodash"
}
}
{
"type": "json",
"example": {
"name": "lodash",
"tool": "pkg-trust-check",
"vulns": [],
"exists": true,
"latest": "4.18.1",
"billing": {
"sku": "pkg_trust_check",
"note": "x402 disabled \u2014 free local / free MCP tier",
"status": "free_tier_or_local",
"x402Enabled": false,
"plannedPriceUsd": 0.005
},
"license": "MIT",
"reasons": [
"exists on registry; no red flags in cheap checks"
],
"verdict": "allow",
"version": "0.2.0",
"ecosystem": "npm",
"deprecated": null,
"disclaimer": "Heuristic only \u2014 not a substitute for Socket/Snyk/enterprise SCA. Free public registry + OSV inputs.",
"provenance": {
"method": "tsx local module import",
"runner": "ToolMint",
"source": "cli-local-run",
"fetchedAt": "2026-10-31T16:19:23.613Z",
"zoneLabel": "America/Chicago"
},
"trustScore": 80,
"description": "Lodash modular utilities.",
"lastPublish": "2026-04-01T21:01:20.458Z",
"maintainers": [
"jdalton"
],
"downloadHint": "636183624 downloads last-month",
"registryError": null,
"typoNeighbors": []
}
}
Examples are the provider's own, not a call we made.
The payout address is shared with 28 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.
How attribution works →30 of 3,206 services (0.9%) in Dev & Code have attributable inflows; 931 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Package trust pack: registry metadata + OSV vulns + typosquat neighbors (query: eco=npm|pypi&name=lodash)
Quoted from PayAI · source record · read 2026-10-31
Attribution blocked
· confidence low
The payout address is also published by 28 other service(s); the volume cannot be attributed to one of them.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is nothing measurable: no price, no attributable address, no receipt. The payout address is also published by 28 other service(s); the volume cannot be attributed to one of them.
No daily history has been archived for this service yet. Open the full daily history →
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://toolmint-pkg-trust.toolmint.workers.dev/check/:eco/:name
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
facilitator.payai.network | 2026-10-31 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
facilitator.payai.network | 2026-10-31 |
| Payment | Provider claim |
1 rail: Base · payee 0xfbF7413bcB3a604936775C96FDbe0b0C9c9E37F5
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
facilitator.payai.network | 2026-10-31 |
| Pricing | Provider claim |
0.005 USDC per call
EvidenceAtomic amount 5000 = 0.005 USDC per call on Base. Netzwerk: Base. |
facilitator.payai.network | 2026-10-31 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
facilitator.payai.network | 2026-10-31 |
| Provider | Provider claim |
toolmint-pkg-trust.toolmint.workers.dev
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
facilitator.payai.network | 2026-10-31 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.