Use GitHub Issues for reproducible community-edition bugs, focused feature requests, documentation improvements, and authorized laboratory workflow questions.
- ARSVIN version or commit;
- application: Publisher or ArSubsv Subscriber;
- Windows and Npcap versions;
- .NET SDK version when building from source;
- workflow type: offline configuration, dry run, live capture, live transmission, SCL, COMTRADE, PCAP, timing, report, installer, or UI;
- exact reproduction steps and expected versus observed behavior;
- evidence environment: automated test, simulator, loopback, isolated laboratory equipment, or approved commissioning environment; and
- the smallest sanitized diagnostic, screenshot, or independent packet-analysis note needed to explain the issue.
Use synthetic or contributor-owned examples whenever practical. Do not post:
- confidential customer, employer, station, or project files;
- credentials, private keys, restricted addresses, or internal network plans;
- production packet captures or private SCL/COMTRADE files without explicit redistribution authority;
- proprietary manuals, support responses, screenshots, reports, binaries, or copied UI assets; or
- exploit details that should be handled through private vulnerability reporting.
Sanitization must preserve the technical condition being reported without exposing protected information.
Community support is best effort and does not imply warranty, response-time commitment, formal conformance assessment, calibrated testing, functional-safety approval, cybersecurity certification, switching authority, or confirmation that an IED consumed multicast traffic.
For security-sensitive issues, follow SECURITY.md.
For proprietary integration, OEM or white-label distribution, private branches, contractual response times, training, warranty, or engineering services, review COMMERCIAL-LICENSE.md and contact the project owner privately through the masarray GitHub profile. The notice is an invitation to discuss terms and grants no additional rights by itself.