addok has not been fully verified yet. No recorded run has produced a verdict yet.

How did Argusic test addok?

On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.

Where is the evidence for addok?

All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

addok

Search engine for address

Not yet testedsource: GitHub homepagePythonMITcommit d928b9e4f6ec

Python, MIT licensed. The project labels itself: address, geocoder, hacktoberfest and search engine.

addok has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict: Not yet tested
Argusic Score: not scored yet
recorded runs: 0
last tested: -
stars: 388
forks: 65
open issues: 37
watchers: 24
size: 1 MB
created: 2014-12-29
last push: 2025-12-23

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-08. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Run history

No recorded runs.

Topics (from GitHub)

address geocoder hacktoberfest search-engine

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/addok.svg)](https://argusic.com/subject/addok)

Questions

Does addok run?: addok has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test addok?: On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for addok?: All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.