zero-mathlib-checker
zero-mathlib-checker is a pre-alpha package for scanning a repository or
fixture tree for direct Mathlib import/dependency evidence.
Mathlib is valuable. This tool is only for projects that intentionally choose a no-Mathlib dependency boundary.
Status
- Version:
0.0.1 - Published for early testing.
- Not a theorem prover.
- Not a safety certifier.
- Not production controller evidence.
- Not a replacement for Mathlib.
- No public theorem/proof/open-problem claim.
Install
python -m pip install zero-mathlib-checker
For repository development:
python -m pip install -e package_candidates/zero_mathlib_checker
Usage
zero-mathlib-checker scan .
zero-mathlib-checker scan . --json
zero-mathlib-checker scan . --allow-policy-text
zero-mathlib-checker scan . --include "*.lean"
zero-mathlib-checker scan . --exclude-dir node_modules
python -m zero_mathlib_checker.cli scan . --json
JSON Output Example
{
"dependency_evidence_count": 0,
"direct_match_count": 0,
"evidence": [],
"passed": true,
"policy_text_count": 0,
"root": "/path/to/repo",
"scanned_files": 1,
"skipped_files": 0
}
Exit Codes
0: no dependency evidence found1: dependency evidence found
Scanner Scope
The scanner recursively reads text-like files, skips common cache/build/vendor directories, and detects:
IMPORT_MATHLIBFROM_MATHLIBMATHLIB_DOT_REFERENCEMATHLIB_DEPENDENCY_DECLARATION
Policy or historical text can be ignored only when the line is explicitly
marked and --allow-policy-text is set.
Relationship To Monogate/MachLib
This package is a small evidence-boundary helper used around Monogate/MachLib workflows. It can support a no-Mathlib dependency policy, but it does not replace repository-specific gates, review, or human judgment.
Limitations
- String-pattern scanner only.
- Does not certify a repository.
- Does not validate proofs or theorem content.
- Does not upload, deploy, or publish anything.
- Does not handle credentials or tokens.
Metadata
Release files for zero-mathlib-checker 0.0.1
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 |
|---|---|---|---|---|
| zero_mathlib_checker-0.0.1.tar.gz | 5.7 kB | Without provenance | Details for zero_mathlib_checker-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zero_mathlib_checker-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for zero_mathlib_checker-0.0.1-py3-none-any.whl |
Total release size: 10.7 kB
Release files / zero_mathlib_checker-0.0.1.tar.gz
| Download URL | zero_mathlib_checker-0.0.1.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
433a5abcd930ae3ee4ffc9e874426456863ed74c6b805700116911a3c66b5102
|
|
BLAKE2b-256 checksum How to use checksums |
2470bdb0497f8e9edbb2e690d1ca61669571aa4160f6f34818d3d34b3365ec30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / zero_mathlib_checker-0.0.1-py3-none-any.whl
| Download URL | zero_mathlib_checker-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d67e38f3aa00201c6944d896d152d78c1911a191139fe9d1c099bd21e036a02b
|
|
BLAKE2b-256 checksum How to use checksums |
04201720809589fd8af2d15dbbf7576f91dad6362c1864ddfa28e7d36e1ba05a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for zero-mathlib-checker 0.0.1
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.