@readystack/security-headers-csp-lint@0.1.8
Not affiliated with ReadyStack (readystack.dev). No new versions are published here. These tools continue under the name Rulestamp, by the team behind getreadystack.com.
Reads security headers and CSP line by line in your config file and names the lines that silently do nothing: retired headers, keywords missing their quotes, directives the browser throws away.
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no lifecycle hooks and no concrete attack behavior. Network activity is tied to the package’s licensing, rule-feed, and limited usage functions.
Decision evidence
public snapshot- package.json names cli.js as the command entrypoint; the complete manifest has no lifecycle hooks.
- License validation sends an explicitly supplied, environment, or saved license key to the package’s licensing service and Polar’s license validation API.
- When a license key is available, the CLI retrieves the product’s rule feed and adds returned rules to its scanner.
- Usage requests send product and command metadata, with telemetry opt-outs and interactive-session checks in place.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @readystack/security-headers-csp-lint@0.1.8.
See all versions of @readystack/security-headers-csp-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/security-headers-csp-lint@0.1.8 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.