Skip to content

Security: NoPanicCom/strictpath-cli

Security

SECURITY.md

Security Policy

Supported Versions

StrictPath CLI is currently prepared for a public beta release.

Version Supported
0.1.x-beta Security fixes
<0.1.0-beta Not supported

Reporting a Vulnerability

Do not report security vulnerabilities through public GitHub issues.

Use GitHub private vulnerability reporting on this repository. If unavailable, contact the maintainers through the security contact listed on the NoPanic profile.

What to Include

  • Clear vulnerability description.
  • Impact and severity.
  • Reproduction steps.
  • Minimal proof of concept when possible.
  • CLI version, Node.js version, package manager version and operating system.
  • Generated project template and command used.

Response Targets

  • Initial acknowledgement: 72 hours.
  • Critical vulnerabilities: target fix or mitigation within 7 days.
  • High vulnerabilities: target fix or mitigation within 30 days.
  • Medium/low vulnerabilities: scheduled in normal release planning.

Security Scope

In scope:

  • CLI command execution safety.
  • Template path traversal and file overwrite behavior.
  • Generated package dependency safety.
  • Secret leakage in generated artifacts.
  • Supply-chain and publish packaging issues.

Out of scope:

  • Vulnerabilities introduced by user-authored business logic after generation.
  • Misconfigured infrastructure not produced by this CLI.
  • Unsupported private/internal templates.

There aren't any published security advisories