The Miser Project Security Policy Statement

miser> SECURITY> 1.4.2 2026-03-02T17:21Z

2026-03-02 Status: At this time there are no code releases for which there need be any vulnerability and exploit concerns.

Current repository content consists mainly of text files and web documentation of an experimental/provisional nature with limited introduction of software for proofs-of-concept. Once there are releases of any kind, their security provisions and status will be updated here.

Most considerations of errors and defects can be handled using the project Issues and Discussions topics. Pull-requests are unwarranted at this time.

Public vulnerability announcements confirm vulnerabilities, reporting their nature, their mitigation, and any actions required by those who may be employing vulnerable software versions. Occassionally, a vulnerability announcement can explain why a particular situation does not qualify as a vulnerability.

Find already-issued public vulnerability announcements, if any, for the Miser project/repository at miser advisories.

See the orcmid.github.io Security Sandbox for a walk-through of what to expect, how to kick off a vulnerability report, and an alternative reporting option.

Securely report an exploitable vulnerability or exposed threat-surface specific to the Miser Project using the vulnerability reporting provision of the Miser Project Security tab.

For independent releases of a fork-/clone-based project, it must be clear that there is no support commitment at the Miser Project and the Security Policy does not extend to the fork/clone.

You are navigating the Miser Project on Github

created 2024-11-07 by orcmid