AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Visualize how a repository's code ages over time with stacked area charts
Translation pending
AI summary · revised during review
Developer toolsPython · JavaScriptGitHub @koaningOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
A repository with some cool charts that tell us about the history of a git repo.
With charts like this you get an idea of how quickly code is rewritten in a repo. You can explore the GitHub pages link or the marimo notebook to learn more.
You can download git_archaeology.py locally to run it, but you can also run it in molab without downloading anything. The marimo notebook contains all dependencies so can just run marimo edit to edit the notebook locally:
You can also run git_archaeology.py as a command-line script:Read the full README ↗A repository with some cool charts that tell us about the history of a git repo.
With charts like this you get an idea of how quickly code is rewritten in a repo. You can explore the GitHub pages link or the marimo notebook to learn more.
You can download git_archaeology.py locally to run it, but you can also run it in molab without downloading anything. The marimo notebook contains all dependencies so can just run marimo edit to edit the notebook locally:
uvx marimo edit git_archaeology.py
You can also run git_archaeology.py as a command-line script:
uv run git_archaeology.py --repo https://github.com/marimo-team/marimo --samples 50
Arguments:
--repo (required) — Repository URL (HTTPS)--samples (optional, default: 100) — Number of commits to sample--file-extensions (optional, default: .py,.js,.ts,.java,.c,.cpp,.h,.go,.rs,.rb,.md) — Comma-separated file extensions to analyze--version-source (optional, default: git tags) — Version source: none, git tags, or pypiAfter generating charts, run make build to update the repository index:
make build
This runs generate_repos_list.py to create charts/repos.json from the available chart files.
Due to browser security restrictions, you cannot open index.html directly from the filesystem. Instead, start a local HTTP server:
uv run python -m http.server
Then open http://localhost:8000 in your browser.
This project was intended for Python projects but the idea is catching on and some folks have started porting this idea to Rust for better performance. If you're keen to explore that, check out https://github.com/czechbol/strata.