kessler-toolkit
Open conjunction assessment for Python: parse CCSDS Conjunction Data Messages, compute collision probability three honest ways, screen a satellite against a catalogue, and triage the results — no MATLAB license required.
Extracted from KESSLER, where the same code powers a live dashboard over the public Space-Track feed.
pip install kessler-toolkit
What's inside
| Module | Purpose |
|---|---|
cdm_parser |
CCSDS 508.0-B-1 KVN CDMs (incl. RTN covariance) and Space-Track cdm_public JSON → typed Cdm |
collision_probability |
Foster 2-D numerical Pc, Chan analytic series (cross-check), covariance-free Max-Pc bound |
propagation |
SGP4 wrapper (TEME), close-approach refinement to sub-second TCA, ground tracks |
screening |
Catalogue screening: altitude sieve → coarse scan → refined TCA + RTN miss components |
risk_engine |
Operator-community risk classes (1e-4 / 1e-5 / 1e-7), urgency scoring, recommended actions |
Quick start
from kessler_toolkit import parse_cdm_kvn, compute_pc
cdm = parse_cdm_kvn(open("conjunction.cdm").read())
result = compute_pc(
miss_m=cdm.miss_distance_m,
hbr_m=20.0,
r_rel_m=cdm.rel_position_rtn_m,
v_rel_ms=cdm.rel_velocity_rtn_ms,
cov1_m2=cdm.sat1.cov_rtn_m2,
cov2_m2=cdm.sat2.cov_rtn_m2,
pc_reported=cdm.pc_reported,
)
print(result.value, result.method, result.pc_type)
# e.g. 2.19e-04 foster-2d computed — with Chan cross-check in result.cross_check
Every result carries pc_type — "computed" (full covariance), "reported"
(source value), or "max" (conservative upper bound) — so downstream code can
never mistake a triage bound for a measurement.
Validated against the closed-form isotropic solution (<0.1% error) and Foster/Chan cross-agreement; screening results are triage-grade (SGP4/GP accuracy limits apply) — not a substitute for operator ephemerides.
Apache-2.0. Orbital data used with KESSLER courtesy of Space-Track.org and CelesTrak.
Metadata
Release files for kessler-toolkit 0.1.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 |
|---|---|---|---|---|
| kessler_toolkit-0.1.1.tar.gz | 15.0 kB | Without provenance | Details for kessler_toolkit-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kessler_toolkit-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for kessler_toolkit-0.1.1-py3-none-any.whl |
Total release size: 31.5 kB
Release files / kessler_toolkit-0.1.1.tar.gz
| Download URL | kessler_toolkit-0.1.1.tar.gz |
|---|---|
| Size | 15.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32439fba1efcf6eb2dc1afae311d4896aa0d6765227e8a11b253864e606667cd
|
|
BLAKE2b-256 checksum How to use checksums |
e0d3800fd122a78d6f0db681199a679bf6f875191892adc14c083edd58bc6a3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.7
|
Release files / kessler_toolkit-0.1.1-py3-none-any.whl
| Download URL | kessler_toolkit-0.1.1-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1fedf908933074fa3b7a5c6a32dbdee1427664e4051d26d732d4883b48bb365d
|
|
BLAKE2b-256 checksum How to use checksums |
f1cb673ede16664458ac87789fd197c0c3c57859631dacdbf13f21c430ece0bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.7
|
Security for kessler-toolkit 0.1.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.