ripcd
Rip audio CDs to FLAC, with metadata. Requires cdparanoia and flac in PATH.
Installation
pip install ripcd
Usage
Usage: ripcd [OPTIONS]
Rip an audio disc to FLAC files.
Requires cdparanoia and flac to be in PATH.
Options:
-D, --drive FILE Optical drive path.
-M, --accept-first-cddb-match Accept the first CDDB match in case of
multiple matches.
--album-artist TEXT Album artist override.
--album-dir TEXT Album directory name. Defaults to artist-
album-year format.
--cddb-host TEXT CDDB host (default is read from the keyring
under gnudb/<user>).
--never-skip INTEGER Passed to cdparanoia's --never-skip=...
option.
-d, --debug Enable debug output.
-o, --output-dir TEXT Parent directory for album_dir. Defaults to
current directory.
-u, --username TEXT Username for CDDB.
-h, --help Show this message and exit.
Metadata lookup uses MusicBrainz first, then CDDB.
The CDDB host can be set in the keyring under the gnudb key for your username, or with
--cddb-host.
1 maintainer
Metadata
1 maintainer
Release files for ripcd 0.0.4
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 |
|---|---|---|---|---|
| ripcd-0.0.4.tar.gz | 13.7 kB | With provenance | Details for ripcd-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ripcd-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for ripcd-0.0.4-py3-none-any.whl |
Total release size: 23.0 kB
Release files / ripcd-0.0.4.tar.gz
| Download URL | ripcd-0.0.4.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
df6b52fc751db3be4da70bec7f4dbae258de6acdecc07e7900e9c2d500cd649e
|
|
BLAKE2b-256 checksum How to use checksums |
7c6e5e4be27ef836460c480f33522766d96c6a39fc65d138a9175cbd60717989
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 23, 2026.
Transparency logRelease files / ripcd-0.0.4-py3-none-any.whl
| Download URL | ripcd-0.0.4-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d82006d8d954fc27e3da67296205ad11eea8e8164893f342af9d7421309847fc
|
|
BLAKE2b-256 checksum How to use checksums |
2b12d855af98f1094db7c3f06364c76b136c34b8834161ba6f2f47a8ec20120c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 23, 2026.
Transparency logSecurity for ripcd 0.0.4
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
Both files in this release have been uploaded with provenance metadata.
Attestation for ripcd-0.0.4.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 May 23, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
