@readystack/manuscript-disclosure-lint@1.0.4
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 reviewed network requests serve package licensing and subscription rule updates. The source does not show the key or project data being sent to an unrelated collector.
Decision evidence
public snapshot- The CLI entrypoint fetches a rule feed at startup, before processing its command-line arguments.
- The feed comes from the package publisher’s getreadystack.com service and uses the configured package license key to retrieve rules.
- The README describes the key as a license for the package’s paid folder-sweep, report, and CI features.
- When license validation is needed, the source sends the key to Polar’s license-validation endpoint.
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.4.
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.4 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.