detect-gh-actions-unused-secrets
Detects secrets that are defined in the repository and are not used in GitHub Actions.
What it does:
- Get repository secrets using GitHub Actions API
- Clone the repository
- Search through the GitHub Actions related files (
.github/workflows/*.yamland.github/workflows/*.yml) and try to find usages of each secret - Report those secrets which are not found
Prerequisites
- GitHub token with
reposcope (GitHub docs)
Installation
pip install detect-gh-actions-unused-secrets
Usage
detect-gh-actions-unused-secrets <token> <owner>/<repo1> <owner/repo2>
--generate-curls
Option to generate a text file with curls to delete all unused secrets in the repositories that were scanned.
detect-gh-actions-unused-secrets <token> <owner>/<repo1> --generate-curls
This command will produce a file called curls.sh that will contain line-by-line curl commands to delete all unused secrets in <owner>/<repo1> repository. This endpoint will be utilized.
1 maintainer
Metadata
1 maintainer
Release files for detect-gh-actions-unused-secrets 0.6.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 | |
|---|---|---|---|---|
| detect_gh_actions_unused_secrets-0.6.0.tar.gz | 4.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| detect_gh_actions_unused_secrets-0.6.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 8.7 kB
Release files / detect_gh_actions_unused_secrets-0.6.0.tar.gz
| Download URL | detect_gh_actions_unused_secrets-0.6.0.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21e78f0a5831f4c8a4bb802b6f28b6cf89ee0649f6487d58bad81bc081b0b589
|
|
BLAKE2b-256 checksum How to use checksums |
4fd21ea4b01fcac3b07a5c581092929099d56f1da8fed221505229ae5321b177
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Release files / detect_gh_actions_unused_secrets-0.6.0-py2.py3-none-any.whl
| Download URL | detect_gh_actions_unused_secrets-0.6.0-py2.py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
08f96320008bd37d5f8aa58b5c88228bc17e18adc5ee082a8470b81e921d062e
|
|
BLAKE2b-256 checksum How to use checksums |
d5d7f76cf15d318cb358d2c2f3274052d6a82b485718a98626a2207859d8193a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for detect-gh-actions-unused-secrets 0.6.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.
