This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Project name on pypi was updated to just carbon-txt
Carbon.txt validator
This validator reads carbon.txt files, and validates them against a spec defined on http://carbontxt.org.
Usage
With the CLI
Run a validation against a given domain, or file, say if the file is valid TOML, and it confirms to the carbon.txt spec.
The following commands assume you are working in a virtual environment:
# parse the carbon.txt file on default paths on some-domain.com
carbon-txt validate domain some-domain.com
# parse a remote file available at https://somedomain.com/path-to-carbon.txt
carbon-txt validate file https://somedomain.com/path-to-carbon.txt
# parse a local file ./path-to-file.com
carbon-txt validate file ./path-to-file.com
# pipe the contents of a file into the file validation command as part of a pipeline
cat ./path-to-file.com | carbontxt validate file
Using UV
If you are not using virtual environments directly, you can use it with uv, which is the recommended way to run the project.
Add carbon-txt-validator to a project with uv add:
uv add carbon-txt-validator
You can now run the command line tool with uv run carbon-txt
Running outside a project
If you have uv installed, you can run the command line tool using the slightly
longer carbon-txt-validator command instead (we need a cli command that shares
the name of the project).
This will download the latest published version from pypi and run the cli:
uv tool run carbon-txt-validator validate ./path/to/file
With the HTTP API
You can also validate carbon.txt files sent over an HTTP API.
# run the carbon-txt validator as a server using the default django server. Not for production
carbon-txt serve
For production, Granian, a
performant webserver is bundled. Pass the flag --server granian to use it.
# run the carbon-txt validator as a server using the production granian server
carbon-txt serve --server granian
Metadata
Release files for carbon-txt-validator 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 | |
|---|---|---|---|---|
| carbon_txt_validator-0.0.4.tar.gz | 68.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| carbon_txt_validator-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.2 kB
Release files / carbon_txt_validator-0.0.4.tar.gz
| Download URL | carbon_txt_validator-0.0.4.tar.gz |
|---|---|
| Size | 68.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a14d2375ee20a4797cbfca4cc21ee31ef265c6ddc44d389c835821b4a50c8e27
|
|
BLAKE2b-256 checksum How to use checksums |
01054d7bfe4ea0bf162a0d54eae4166bd6a0c20fe5c2a199bc83e172fc54087f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0rc2
|
Release files / carbon_txt_validator-0.0.4-py3-none-any.whl
| Download URL | carbon_txt_validator-0.0.4-py3-none-any.whl |
|---|---|
| Size | 20.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
249493854b2741883ca7f1536f1de363b983c35a5973456972f2ed6b619b6c32
|
|
BLAKE2b-256 checksum How to use checksums |
69d9935337677b8e1db42d040803163533e81172d4ff4ce9a1473f98b7e495f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0rc2
|
Security for carbon-txt-validator 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.
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.