CRA 24/72/14 Reporting Lint (Article 14)
No liveness check has reached it yet; it is registered on the VS Code Marketplace and has been in the index since 16 Sep 2026. How this is checked
A VS Code extension that checks SECURITY.md files, vulnerability disclosure policies, and incident runbooks against Article 14 reporting timelines under the EU Cyber Resilience Act. It performs 18 offline checks for early-warning, notification, and final-report requirements for security and compliance teams.
Inferred · not functionally tested
Overview
5 featuresPurpose: Helps security teams verify that incident documentation reflects the EU Cyber Resilience Act's 24-hour, 72-hour, and 14-day reporting deadlines.
Inferred · not functionally tested
Audience: software security and compliance teams
Inferred · not functionally tested
Functions: Unknown
Interfaces: API: unknown · MCP: unknown · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: free · license: Proprietary · platforms: WEB · deployment: browser, windows, macos, linux
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: unknown.
CRA 24/72/14 Reporting Lint (Article 14) sits in PulseGate's Static analysis & linters category. Inferred · not functionally tested: It helps security teams verify that incident documentation reflects the EU Cyber Resilience Act's 24-hour, 72-hour, and 14-day reporting deadlines. Inferred · not functionally tested: CRA 24/72/14 Reporting Lint (Article 14) is a B2B product aimed at software security and compliance teams. Basis unknown · not verified: CRA 24/72/14 Reporting Lint (Article 14) is free to use. Basis unknown · not verified: It ships for the web, Windows, macOS, and Linux.
Behind CRA 24/72/14 Reporting Lint (Article 14) is ReadyStack, and it first shipped in 2026. Inferred · not functionally tested: Key capabilities include 18 compliance checks, markdown linting, and CRA deadline validation.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- 18 compliance checks
- Markdown linting
- CRA deadline validation
- Offline operation
- Security documentation checks
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed16 Sep · 15:16 UTCCRA 24/72/14 Reporting Lint (Article 14) seen via VS Code MarketplaceSource: VS Code Marketplace · Open
Frequently asked questions about CRA 24/72/14 Reporting Lint (Article 14)
- What does CRA 24/72/14 Reporting Lint (Article 14) do?
- Inferred · not functionally tested: CRA 24/72/14 Reporting Lint (Article 14) helps security teams verify that incident documentation reflects the EU Cyber Resilience Act's 24-hour, 72-hour, and 14-day reporting deadlines. It is catalogued under Static analysis & linters on PulseGate.
- Who should use CRA 24/72/14 Reporting Lint (Article 14)?
- Inferred · not functionally tested: CRA 24/72/14 Reporting Lint (Article 14) is a B2B product built for software security and compliance teams.
- Is CRA 24/72/14 Reporting Lint (Article 14) free?
- Basis unknown · not verified: Yes — CRA 24/72/14 Reporting Lint (Article 14) is free to use.
- What platforms does CRA 24/72/14 Reporting Lint (Article 14) run on?
- Basis unknown · not verified: CRA 24/72/14 Reporting Lint (Article 14) runs on the web, Windows, macOS, and Linux.
- Is CRA 24/72/14 Reporting Lint (Article 14) still maintained?
- Unverified. CRA 24/72/14 Reporting Lint (Article 14) has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
- Who develops CRA 24/72/14 Reporting Lint (Article 14)?
- CRA 24/72/14 Reporting Lint (Article 14) is developed by ReadyStack.
- How long has CRA 24/72/14 Reporting Lint (Article 14) been around?
- CRA 24/72/14 Reporting Lint (Article 14) first shipped in 2026.
Similar projects
Closest matches by what these projects do