Skip to main content

fixprove (Python engine, open-core)

FixProve deterministically verifies that every import, symbol, method, and API call in your code — Python or TypeScript/JavaScript — resolves against your real, installed dependencies. No LLM calls, no false-positive-prone heuristics: an AST-level resolver checks a reference set against a knowledge base built from what's actually on disk.

pip install fixprove
fixprove /path/to/your/project

fixprove check /path/to/your/project (the same form the npm wrapper and fixprove.dev's own install instructions use) also works here — both forms are identical, so pip-only users don't need to know the npm package exists to follow the site's install block. See KS-TRACE PRIORITY-TRACKER-2026-09-11-P0-CLI-SYNTAX in cli.py for why.

Exit codes: 0 clean, 1 unresolved symbol(s) found, 2 usage/setup error — designed to drop straight into a CI gate.

This is the same engine that powers the FixProve GitHub App, which posts this check as a blocking status directly on your pull requests. Analysis runs in your CI — the App does not read or store your repository's source code. Only specific finding fragments (file paths, line numbers, and the unresolved expression) transit our endpoint, encrypted and never persisted, to post the check annotation; see the Privacy Policy for the full description. This CLI is the open-core, self-hosted way to run the identical deterministic core locally or in your own pipeline.

Scope (current)

  • Python: imports, call targets, attribute chains, checked against installed packages' real public API.
  • TypeScript/JavaScript: imports/re-exports/call targets/attribute chains, checked against installed npm packages' .d.ts declarations.
  • Known limitation: packages using TypeScript module augmentation (e.g. @types/lodash) are safely skipped (never flagged, but also not fully checked) rather than guessed at — see the engine's own Keystone Reports (KS-REPORT-1.4-ts-resolver.md in the source repository) for the full accuracy/limitation writeup.

License

MIT — see LICENSE. This package is the open-core component of FixProve; the GitHub App and web dashboard are proprietary (see the source repository's root NOTICE.md).

Metadata

Release files for fixprove 0.1.14

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fixprove 0.1.14
File Size Uploaded
fixprove-0.1.14.tar.gz 52.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for fixprove 0.1.14
File Interpreter ABI Platform
fixprove-0.1.14-py3-none-any.whl Python 3 none any Details

Total release size: 105.4 kB

Release files / fixprove-0.1.14.tar.gz

Download URL fixprove-0.1.14.tar.gz
Size 52.4 kB
Tags Source
SHA-256 checksum
How to use checksums
303d5701c6344e68d07ef7fb743c27921a6c69a37e7e9c7a61246adb176a6c37
BLAKE2b-256 checksum
How to use checksums
0a5eba4ec73458ecbf8f6e300b96361b72ff340bf1598f0ebb236dbfbbc9aa10
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 12, 2026.

Transparency log

Release files / fixprove-0.1.14-py3-none-any.whl

Download URL fixprove-0.1.14-py3-none-any.whl
Size 53.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
748df36cdbcff0542e3c116fa3a5452683a679d4db1cb6215f336bd5b3f64530
BLAKE2b-256 checksum
How to use checksums
7edeea2b60e3e3b0fa5dc29455a6940adbeef062f5b8647c036cb0325b0741a5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 12, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.16

2 release files

0.1.15

2 release files

This release

0.1.14 This release

2 release files

0.1.12

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.0

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page