Keeping the raw payload next to the derived report
Check a token's security and rug-pull risk, and keep what the check said.
Enter a contract address, get a markdown report from GoPlus’s Token Security and Rug Pull Detection APIs. The report is the visible half; the archive is the half worth recording.
Every run stores the raw JSON each API returned, alongside the contract address and the date, in SQLite. Not the parsed fields, not a score, the actual payload. That costs almost nothing and changes what the tool is. A report-only version tells you what it thought that day. Storing payloads means a later change in how risk is interpreted can be re-run across everything already collected, and a disagreement about a past report is settled by looking rather than arguing.
The limitation needs stating plainly, because a clean report invites more confidence than it earns. This reports one vendor’s opinion. The archive is a record of what GoPlus said, not of what was true.
Reports are named by token symbol and date, which collides, because symbols are not unique and treating them as filenames assumes they are.
The README links to a DYOR note and says results are not financial advice.