@readystack/lectura-facil-lint-es
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.
12 reglas de lectura fácil para guías y formularios de trámite (RD 707/2026, UNE 153101)
This report shows the evidence for @readystack/lectura-facil-lint-es@1.0.3. 0 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry to its own service, which warrants a warning under the review rules. The observed event contains only package-use metadata, so the evidence does not support classifying it as data exfiltration or blocking publication.
Decision evidence
public snapshot- After free CLI checks, the program sends a usage event in interactive sessions unless telemetry is disabled.
- The event contains only the event type, package slug, CLI source, and free-use reason, and goes to getreadystack.com/api/ev.
- The README describes the free and licensed features but does not disclose this usage telemetry.
- The event is limited to interactive sessions and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.
- The telemetry payload does not include credentials, host or user identity, file contents, or project paths.
- License-key validation is consistent with the package’s documented licensing model.
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/lectura-facil-lint-es@1.0.3.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/lectura-facil-lint-es@1.0.3 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.