pleno-secret-scanner (Python)
Python CLI that scans SaaS content for leaked secrets, backed by saas-retriever for source collection (API-only — no scraping) and a pluggable detection backend (trufflehog, gitleaks, or a tiny built-in regex set).
The Go binary in this repo (cmd/pleno-secret-scanner) remains for
filesystem-only scans; the Python package is the path forward for SaaS.
Install
uv tool install pleno-secret-scanner
# or
pipx install pleno-secret-scanner
Usage
# Scan an entire GitHub org (code + issues + PRs across every repo)
GITHUB_TOKEN=ghp_... pleno-secret-scanner scan github --owner plenoai
# Scan a single repo, only code, with trufflehog verification
pleno-secret-scanner scan github --owner plenoai --repo saas-retriever \
--resource code --backend trufflehog
# Issue + PR conversations only (skip code)
pleno-secret-scanner scan github --owner plenoai \
--resource issues --resource prs
# SARIF output for GitHub code-scanning ingestion
pleno-secret-scanner scan github --owner plenoai \
--format sarif > findings.sarif
Auth resolution: --token → GITHUB_TOKEN env var → gh auth token.
Anonymous works for public content but is rate-limited to 60 req/h.
Backends
| Backend | Verifies | System dep |
|---|---|---|
| trufflehog | yes (per-detector) | trufflehog CLI on PATH |
| gitleaks | no | gitleaks CLI on PATH |
| native | no | none — bundled regex set (AWS, GitHub PAT, Slack bot, OpenAI, Anthropic) |
Connectors
Anything saas-retriever provides. v0.1.x ships github with
org-wide enumeration + per-repo code / issues / PRs (with comments and
unified diffs). Slack / Jira / Confluence / Notion / GitLab / Bitbucket
return as standalone API connectors in subsequent saas-retriever
releases.
Release
Tag py-vX.Y.Z triggers PyPI trusted publishing via GitHub Actions.
Metadata
Release files for pleno-secret-scanner 0.4.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 | |
|---|---|---|---|
| pleno_secret_scanner-0.4.0.tar.gz | 10.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pleno_secret_scanner-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.2 kB
Release files / pleno_secret_scanner-0.4.0.tar.gz
| Download URL | pleno_secret_scanner-0.4.0.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfa65ef30258d6470dded3c6373a4008908ab46622c544accd9c2eff3992f8e8
|
|
BLAKE2b-256 checksum How to use checksums |
055b84749b7c87870aa24bcb80cfbccc0853a89e3c72c809e5efc623882d7145
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 May 6, 2026.
Transparency logRelease files / pleno_secret_scanner-0.4.0-py3-none-any.whl
| Download URL | pleno_secret_scanner-0.4.0-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f395466d834a4b4df824ac10101a63a9e72b7106f605219e34f3a4a2929322d
|
|
BLAKE2b-256 checksum How to use checksums |
81272635c670bc8d3b6bc754b84da082ac16b50e52a3a83dc5053ee803b0fd30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 May 6, 2026.
Transparency log