SECURE//REPO
Repository security auditor with a command-line console and a neural-map GUI.
Static code analysis · secret detection · library & supply-chain intelligence · repository structure mapping · optional compliance evidence (OWASP, PCI DSS, ISO 27001, SOC 2, GDPR, HIPAA, NIST SSDF)
What it does
Point it at a Git repository (the one you are in, a local path or a Git URL, including private ones) and it audits it read-only: it never runs the audited code and never installs its dependencies.
| Capability | Details |
|---|---|
| Static analysis | 175 rules for Python, JavaScript/TypeScript, Java/Kotlin, C#, PHP, Go, Ruby, C/C++, Rust, shell, Dockerfiles, Kubernetes, Terraform and CI pipelines. Python gets syntax-tree analysis with taint tracking, JavaScript/TypeScript a data-flow pass. |
| Secrets | Cloud keys, tokens, private keys, connection strings, high-entropy credentials, sensitive files. Always redacted in the output. |
| Libraries | 25+ manifest and lock formats; every library checked against OSV.dev and deps.dev; versions resolved even without a lockfile. Private package names can be kept off the network. |
| Reports | A timestamped folder with HTML, JSON, SARIF, Markdown, CSV, a CycloneDX SBOM and an integrity manifest, written outside the audited repository by default. |
| Console and GUI | A live terminal dashboard (--theme plain for a sober one) and a local web app with a neural map and a structure treemap that explain each weakness and its fix. |
| CI-friendly | --fail-on, --baseline (fail only on new findings), --since origin/main (only changed files), SARIF for code scanning. |
| Learns from you | Mark false positives and accepted risks once; they are re-applied on every scan. |
| Optional compliance evidence | Maps findings to 7 frameworks as supporting evidence, never as a certification. |
Quick start
git clone https://github.com/Wissen01720/Secure_Repo.git
cd Secure_Repo
./run.sh scan /path/to/repo # Windows: .\run.bat scan C:\path\to\repo
./run.sh gui # the graphical interface
The launcher creates a private virtual environment on the first run. Inside a Git repository, ./run.sh alone opens
the interactive console. Python 3.10 or newer and Git are required. More options (pipx, from source, updating):
Installation.
secure-repo scan . --yes --plain --no-menu --baseline baseline.json --fail-on high # a CI gate for new problems only
How accurate is it?
Measured on code the authors did not write: four public projects pinned to a commit (NodeGoat, DVPWA,
Vulnerable-Flask-App and the clean library requests), every finding reviewed by hand.
| Result | |
|---|---|
| Precision, findings of medium/high confidence | 73 % |
| Precision, every finding (tests and low confidence included) | 60 % |
| Documented weaknesses found | 26 of 28 (93 %) |
Small sample, so read it as a floor of evidence and not as a guarantee: the details, the misses and how to reproduce it are in How the analysis works. The limits of a static analyzer (what it cannot see) are in Privacy, trust model and limitations.
Documentation
| Document | What is in it |
|---|---|
| Installation | Requirements, launchers, pipx, from source, in-place updates |
| Command-line guide | Step by step walkthrough, CI/CD usage, private and organization repositories |
| How the analysis works | Engines, accuracy, languages, scoring, false-positive reduction, compliance |
| Command and report reference | Every flag and every file of a report folder |
| Graphical interface | The neural map, structure boxes, triage and downloads |
| Privacy, trust model and limitations | What leaves your machine, how the audited repository is treated, suppressions, limits |
| Troubleshooting | Common problems and fixes |
| Development | Project layout, tests, adding a rule |
| Releasing | Versions, tags, GitHub releases and publishing to PyPI |
Rules of engagement
Only audit repositories you own or have explicit, written permission to assess.
Secure Repo is built for defenders and enforces that posture:
- It never executes the audited code, never installs its dependencies and never exploits a finding.
- It asks you to confirm your authorization before every engagement (
--yesconfirms it in automation). - Detected secrets are redacted in the terminal, the GUI and every report.
- Git runs hardened: hooks disabled,
ext::transport blocked, shallow clones, LFS downloads skipped.
Using the tool to steal information or for any malicious purpose is forbidden by the license.
License
Copyright © 2026 Wissen01720. All rights reserved.
Secure Repo is distributed under the Secure Repo Ethical Source-Available License: you may use it, study it and use its reports (also inside your company) for lawful, authorized security work. You may not use it to access code without permission, steal or misuse the information it finds, attack systems, remove the attribution, claim authorship, sell it or publish modified versions without permission. Read the full LICENSE. It is source-available, not open source: if your organization requires an OSI-approved license, contact the author.
Metadata
Release files for secure-repo 1.3.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 | |
|---|---|---|---|---|
| secure_repo-1.3.0.tar.gz | 330.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| secure_repo-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 657.7 kB
Release files / secure_repo-1.3.0.tar.gz
| Download URL | secure_repo-1.3.0.tar.gz |
|---|---|
| Size | 330.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4bfef90264d7d1683e65698044d70434b5a6027bcb756582c96b332ead15adc
|
|
BLAKE2b-256 checksum How to use checksums |
3adef977df48c2b306ef2cdaeb11b9d8d61b45b1efde94c788ea2c1b853034d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / secure_repo-1.3.0-py3-none-any.whl
| Download URL | secure_repo-1.3.0-py3-none-any.whl |
|---|---|
| Size | 326.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ffe71adc8572e10ab60054660d265af2cb6ad6f693742c31a7097f0271fe4c85
|
|
BLAKE2b-256 checksum How to use checksums |
891e55b9408958918eb029c2be1d83269d8ffbb187ba3631480acbd77cd6d272
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for secure-repo 1.3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for secure_repo-1.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA 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.