Jepeta Risk Intelligence

Jepeta Base Risk Snapshot — October 2026

Observed Base token risk signals from 184 unique HIGH/MEDIUM-quality Jepeta observations in October 2026.

Research question: What risk decisions and summary-coded risk signals were observed in usable Jepeta Base token scans this month?

Observation window: Oct 1, 2026, 04:05 AM UTC → Oct 7, 2026, 04:46 PM UTC. Page generated Oct 7, 2026, 04:47 PM UTC from the public research API.

Sample and provenance

Dataset: Jepeta persisted risk observations, aggregated from private rows. Methodology version: 2.0.0. Latest HIGH/MEDIUM-quality Jepeta risk observation per unique Base token within the month. This is an observational Jepeta sample, not a random or representative census of Base.

184unique usable tokens
50.14average risk score
8.15%PASS
91.30%WARN
0.54%BLOCK

Observed signals

SignalTokensShare of sample
Summary-coded honeypot detection00.00%
Summary-coded mintability warning31.63%
Summary-coded high holder concentration137.07%
Summary-coded liquidity warning126.52%
Summary-coded market-data warning10.54%

How to interpret this

This is original Jepeta telemetry, not a market-wide prevalence estimate. The sample contains tokens observed by Jepeta and passing the HIGH/MEDIUM data-quality gate. Repeated scans do not overweight a token: only its latest usable observation in the month is counted. Signal counts are derived from configured reason codes in Jepeta summaries, not independent measurements of every token property.

Limitations

  • This is an observational Jepeta sample, not a random or representative census of all Base tokens.
  • Percentages describe the usable tokens observed by Jepeta in this period and must not be generalized to the whole Base ecosystem.
  • One latest HIGH/MEDIUM-quality observation per token is used to avoid repeated scans overweighting a token.
  • WARN and BLOCK are Jepeta policy outcomes, not investment recommendations or proof of fraud.
  • PASS means no configured WARN/BLOCK condition was observed in available evidence; it is not a safety guarantee.
  • Summary reason-code counts are Jepeta policy outputs, not exhaustive measurements of token properties.
  • Historical source observations may predate the current methodology reference; they are not retroactively rescored as V5 verdicts.
  • Raw observation rows are private; the public aggregate does not permit independent rederivation of source counts or past rolling-month states.

Reproducibility

Query version 20260924170500_t040_geo_risk_intelligence is published as aggregation.sql and selects the latest usable observation per token in the month. The published aggregate JSON permits recalculating percentages from counts. Raw observation rows are private, so source counts and an earlier rolling-month state cannot be independently rederived from public data.

User-facing methodology · Machine methodology · Sources · Selected public evidence · Research API · Run a current scan