PyCot
Python Cursor on Target LibrarySummary
PyCot is developed to assist and streamline integration with programs that utilize Cursor on Target (CoT). This tool seeks to help generate, validate, and parse XML data that is defined from either MITRE or the MIL-STD.
Why?
I needed an easy way to interface with CoT messages, I could not find one available.
Usage
pipx install PyCot
import CoT
import datetime
import socket
now = datetime.datetime.now(datetime.timezone.utc)
stale = now + datetime.timedelta(minutes=2)
# Generate new Cursor on Target Event
py_cot = CoT.Event(
version="2.0",
type="a-u-G-U-U-S-R-S",
access="Undefined",
uid="Debug.Python",
time=now,
start=now,
stale=stale,
how="h-g-i-g-o",
qos="2-i-c",
point=CoT.Point(lat=90, lon=90, hae=9999999, ce=9999999, le=9999999),
detail={"contact": {"callsign": "Debug.Python"}},
)
# Your TAK IPv4 / Port
TAK_IP = "x.x.x.x"
TAK_PORT = 9000
# Sending UDP -> TAK Insecure Anonymous Port
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
sock.connect((TAK_IP, TAK_PORT))
sock.sendall(bytes(py_cot.xml(), encoding="utf-8"))
Release files for PyCoT 3.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 |
|---|---|---|---|---|
| pycot-3.0.1.tar.gz | 25.1 kB | With provenance | Details for pycot-3.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pycot-3.0.1-py3-none-any.whl | Python 3 | none | any | Details for pycot-3.0.1-py3-none-any.whl |
Total release size: 49.7 kB
Release files / pycot-3.0.1.tar.gz
| Download URL | pycot-3.0.1.tar.gz |
|---|---|
| Size | 25.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
589850821dce09d6e437c78eab5812a79651759b5ca24434832a47d2b44537bd
|
|
BLAKE2b-256 checksum How to use checksums |
678786ce7a30d864b91c128c4e95f34501bab4011c69d40e2512f05e63162b07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 29, 2025.
Transparency logRelease files / pycot-3.0.1-py3-none-any.whl
| Download URL | pycot-3.0.1-py3-none-any.whl |
|---|---|
| Size | 24.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
48d66b2d3d1816416d78e6fcad5c459f91b4f84495102b55066898cae5bf7c93
|
|
BLAKE2b-256 checksum How to use checksums |
bc3988c9fdfedc2c7e431c786b4914b83e4c9aa97d7cdc58ac2940c882d4bafa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 29, 2025.
Transparency logSecurity for PyCoT 3.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pycot-3.0.1.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 Apr 29, 2025.
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.
