@readystack/manuscript-disclosure-lint@1.0.5
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.
16 rules that catch the statements a journal desk-rejects you for — in your .tex or .md, before you submit
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends undisclosed runtime usage telemetry to the vendor after interactive free scans, contrary to the README’s claim that nothing is uploaded. The inspected event contains no manuscript contents or credentials, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- The package exposes cli.js as its command-line entry point, and a normal free scan calls pingUse after processing files.
- On an interactive free run, unless a telemetry opt-out or CI variable is set, pingUse sends a POST to getreadystack.com/api/ev containing the event type, package slug, CLI source and reason.
- The README says “Nothing is uploaded,” which does not disclose this runtime usage event.
- The telemetry payload shown contains no manuscript contents, credentials, hostnames or usernames.
- The free scan reads local files, and the usage ping is limited to interactive terminal sessions with opt-outs.
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/manuscript-disclosure-lint@1.0.5.
See all versions of @readystack/manuscript-disclosure-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/manuscript-disclosure-lint@1.0.5 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.