A PyPI password or token is stored in plain text (‹path›)
What this means
‹path› holds ‹plaintext tokens› upload credential(s) in plain text. Whoever copies the file can publish a release of your package.
How to fix it
- Revoke the token on PyPI and create a new one scoped to a single project.
- Let twine read it from your keychain instead:
keyring set https://upload.pypi.org/legacy/ __token__, then remove the password line. - For releases from CI, use PyPI trusted publishing, which needs no stored token.
Check it yourself
Run a scan and look for BLWK-CRED-007 in the results:
sh
bulwark scanInstalled the standalone CLI package instead of the app? The command is bulwarkctl.
How Bulwark decides
Bulwark reads credential_stores and reports this check when:
text
kind == "pypirc" and plaintext_tokens > 0If a value can't be read, Bulwark reports the check as undetermined rather than passing it. View the rule source.
References
Related checks
- A long-lived AWS access key is stored on disk ·
BLWK-CRED-001 - Git stores passwords and tokens in plain text (‹path›) ·
BLWK-CRED-002 - Docker registry logins are stored in the config file ·
BLWK-CRED-003 - A credential file can be read by other users ·
BLWK-CRED-004 - Secrets are written into a shell startup file (‹path›) ·
BLWK-CRED-005 - An npm token is stored in plain text (‹path›) ·
BLWK-CRED-006