codeatlas-bundle
Bundle CodeAtlas architecture maps into any repository so the map is versioned alongside the code.
codeatlas-bundle runs the deterministic CodeAtlas analysis, renders the docs
(Markdown + HTML by default), writes them under a configured directory, and can
commit the result. It is pure Python and works for repositories in any language
CodeAtlas supports (Python, Rust, Go, JavaScript/TypeScript).
Install
pip install codeatlas-rs codeatlas-bundle
Connect a repository
cd my-repo
codeatlas-bundle init # writes codeatlas.json
codeatlas-bundle build # generates docs/codeatlas/
codeatlas-bundle build --commit # generate and commit
codeatlas.json:
{
"project_name": "my-repo",
"output_dir": "docs/codeatlas",
"formats": ["markdown", "html"],
"depth_cap": 3,
"include_analysis": false
}
formats: any ofmarkdown,html,mdx,rst.include_analysis: whentrue, also commit the rawanalysis.json,fingerprint.json, andfile_coverage.jsonsidecars (the raw analysis contains a generation timestamp, so this produces a larger diff each run).
CI: keep the map fresh
# .github/workflows/codeatlas.yml
name: CodeAtlas
on:
push:
branches: [main]
permissions:
contents: write
jobs:
bundle:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: "3.12"
- run: pip install codeatlas-rs codeatlas-bundle
- run: git config user.name "codeatlas" && git config user.email "codeatlas@users.noreply.github.com"
- run: codeatlas-bundle build --commit
- run: git push
To gate a pull request instead of committing, use codeatlas-bundle check,
which exits non-zero when the committed bundle is stale.
Python API
from codeatlas_bundle import bundle, check
result = bundle("path/to/repo", commit=True)
print([str(p) for p in result.files])
is_current, changed = check("path/to/repo")
Metadata
Release files for codeatlas-bundle 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 |
|---|---|---|---|---|
| codeatlas_bundle-0.1.0.tar.gz | 6.3 kB | Without provenance | Details for codeatlas_bundle-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| codeatlas_bundle-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for codeatlas_bundle-0.1.0-py3-none-any.whl |
Total release size: 13.8 kB
Release files / codeatlas_bundle-0.1.0.tar.gz
| Download URL | codeatlas_bundle-0.1.0.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa1ed483c041b05b53dce5bf57afc39caf43f6da7d729cf5e276ec53c195dfe1
|
|
BLAKE2b-256 checksum How to use checksums |
bae205690e42819000455960fef16ef838df4cdcbcfa82cd6f7f2d20952c761a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / codeatlas_bundle-0.1.0-py3-none-any.whl
| Download URL | codeatlas_bundle-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1633d78d8573cbfe4dbd77563b918a11993f0e28ccc9d70826b37d6782e82364
|
|
BLAKE2b-256 checksum How to use checksums |
76353ad8b29d3793dfab6b1f9befce3ebe6102376ce70dda0831521983567a07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for codeatlas-bundle 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.