Skip to content

Security: patcGM/closurectl

SECURITY.md

Security policy

Supported versions

Only the latest tagged version and the current default branch receive security fixes.

Reporting a vulnerability

Please do not open a public issue for vulnerabilities that could expose credentials, bypass artifact validation, forge receipts, or cause unsafe provider actions. Use GitHub private vulnerability reporting and include:

  • affected version or commit;
  • impact and threat scenario;
  • minimal reproduction;
  • whether credential material may have been exposed;
  • suggested remediation, if known.

The project will acknowledge a complete report within seven days and coordinate disclosure based on impact and fix availability.

High-priority areas

  • receipt forgery or signature confusion;
  • canonicalization inconsistencies;
  • plaintext credential persistence;
  • command injection in provider adapters;
  • destructive behavior in a read-only command;
  • preview/confirmation substitution or stale-preview execution;
  • repeated mutation after a timeout or process crash;
  • observer credentials that are not independent of the mutation identity;
  • unescaped provider metadata in generated HTML reports;
  • minimum-cut errors that incorrectly report CLOSED;
  • key overwrite or unsafe private-key handling;
  • provider responses being interpreted as stronger evidence than they are.

Safe testing

Use only accounts, organizations, packages, and infrastructure you own or have explicit authorization to test. Do not include real credentials or personal incident data in reports. A local demonstration can be generated with:

closurectl demo --dir closurectl-demo

Security posture

Version 1.0.0 has attended live adapters for exact GitHub Actions workflow/run and npm token targets. Execution still refuses to proceed without a fresh preview digest, independent observer/recovery credentials, and a new journal path. Inventory and observation commands remain read-only.

The adapters are intended for attended incident response only. Do not grant broader permissions than the exact disposable or incident scope requires. npm revocation may take up to one hour to propagate, and a provider acceptance response is never treated as closure evidence.

There aren't any published security advisories