| Branch | Status |
|---|---|
main |
Supported beta/community edition |
legacy |
Archived previous public state, not supported for new fixes |
Please report suspected vulnerabilities privately to info@acnc.dromation.com instead of opening a public issue.
Include:
- affected version or commit
- operating system
- steps to reproduce
- expected behavior
- actual behavior
- logs or screenshots if available
ACNC is software for analysis and documentation workflows. It is not a certified safety controller and must not be treated as one.
Do not connect computer ports directly to CNC signal lines. Physical connections require an isolated interface with appropriate galvanic isolation, surge protection, voltage protection, and correct power-domain separation.
Software write safeguards are defense-in-depth only. They do not make unsafe wiring safe.
The application is designed around these rules:
- reads and scans are separate from writes
- writes require an explicit prepare/confirm flow
- writes are gated by confidence state
- dry-run paths must not touch hardware
- confirmation re-checks current confidence from the database
- write verification and rollback support are part of the backend workflow
Any change that weakens these rules should be treated as a high-risk security and safety issue.
Kivy/KivyMD UI tests require a real or virtual display. On headless Linux, use:
xvfb-run -a python3 -m unittest discover -s tests -vOn Windows, close any running ACNC/Kivy app before running the full UI test suite.