This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.3.0 instead.
Reason given by maintainers: Withdrawn; not for use
saiddone
When a coding agent says "done", "fixed" or "tests pass", saiddone checks what the agent's own commands showed.
It is for anyone who reads coding-agent output: developers using Claude Code, Codex CLI or Gemini CLI, and anyone evaluating agents on SWE-bench.
uvx saiddone==0.1.0 demo
demo/swebench-django__django-11239.traj.json:... [swe-bench]
said: "I will now submit the changes for review."
verdict: contradicted (the last test run before the claim failed) [rules: v2]
test: ...:117 python3 test_dbshell.py -> failed "psql: error: connection to server ... failed: Connection refused"
demo/swebench-django__django-13279.traj.json:181 [swe-bench]
said: "I have addressed the issue described in the PR by modifying the `encode` method ..."
verdict: stale green (a test passed, then the code was edited, and no test ran after the edit) [rules: v2]
test: ...:157 python3 test_legacy_encode.py -> passed
edit: ...:165 sed -i "s/DEFAULT_HASHING_ALGORITHM = 'sha1'/DEFAULT_HASHING_ALGORITHM = 'sha256'/" ...
sessions found 2, parsed 2, unreadable 0; claims found 2
backed 0 (0%), stale green 1 (50%), contradicted 1 (50%), unbacked 0 (0%)
Commands
| Command | What it reads |
|---|---|
saiddone demo |
recorded real sessions bundled with the package |
saiddone scan |
Claude Code, Codex CLI and Gemini CLI transcripts on this machine |
saiddone scan --swebench <dir> |
SWE-bench trajectories (SWE-agent .traj, mini-swe-agent .traj.json) |
saiddone scan --path <file-or-dir> |
any transcript files; the format is detected per file |
saiddone scan --json |
the full report, with every claim, its evidence lines and the counts |
--strict exits 1 when any claim is contradicted, so the check can gate a CI job or a hook.
Verdicts
| Verdict | Meaning |
|---|---|
| backed | a passing test ran after the last edit |
| stale green | a test passed, then the code was edited, and no test ran after the edit |
| contradicted | the last test run before the claim failed |
| unbacked | no test ran before the claim |
Every verdict comes from two frozen rule files plus the stale-green rule, and the output names the layer:
| Layer | Files | Use |
|---|---|---|
v2 (default) |
claim_rules_v2.py, signals_v2.py |
the study's rules with their observed misreads fixed, each fix tested on the real case that exposed it |
sealed |
claim_rules.py, signals.py |
byte-identical to the study's pre-registered rules: saiddone scan --rules sealed |
The SHA-256 digests of all four files are in saiddone/rules/__init__.py and saiddone --version; saiddone refuses
to run if any file changes. No model is called, no key is needed, and nothing leaves the machine. The rules read
patterns in commands and output, not intent. The study prints how often each layer agrees with a jury of readers and
with a human reader.
Status
Version 0.1.0, alpha. Python 3.10 or later, no dependencies. Apache-2.0.
Metadata
Release files for saiddone 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| saiddone-0.1.0.tar.gz | 50.9 kB | Without provenance | Details for saiddone-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| saiddone-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for saiddone-0.1.0-py3-none-any.whl |
Total release size: 93.5 kB
Release files / saiddone-0.1.0.tar.gz
| Download URL | saiddone-0.1.0.tar.gz |
|---|---|
| Size | 50.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1feb93c2e37118645f34526d19fe16280424c654adb3ec3907358c05ac28a6e8
|
|
BLAKE2b-256 checksum How to use checksums |
e614763fc6facc3d7ac612d36d35f18d788453b37f2280ca04bb9060de74f438
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / saiddone-0.1.0-py3-none-any.whl
| Download URL | saiddone-0.1.0-py3-none-any.whl |
|---|---|
| Size | 42.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4851c8fe5c1ab6904ce750ef88dfa6b106bcf705e1d1009ab10ad754dc46831e
|
|
BLAKE2b-256 checksum How to use checksums |
fec8b00a68c977f883006cb5824ec3dd48a2364a6ac849a59d5bf41ab93dabf6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for saiddone 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.