@readystack/webfont-license-audit@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.
The 12 licence questions a foundry audit letter asks, run against your CSS
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends undisclosed runtime usage telemetry by default in interactive sessions, although it limits the payload to basic event metadata and offers opt-outs. This warrants a warning, but the reviewed code does not show credential theft or project-data exfiltration.
Decision evidence
public snapshot- A free CLI scan calls pingUse() after it finishes, and that event is sent to the vendor’s /api/ev endpoint.
- The event contains only the event type, package slug, CLI/MCP source, and use or paywall reason; it is gated by terminal/MCP use and can be disabled with documented environment variables in the source.
- License checks send a supplied or stored license key to the vendor’s license endpoint for validation.
- The event payload does not include scanned file contents, paths, credentials, or environment values.
- License validation and rule-feed requests go to the package vendor or the identified license provider and serve licensing or product-rule functions.
- The package exposes a CLI for scanning font-license issues, and the flagged behavior is not triggered by an install lifecycle script.
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/webfont-license-audit@1.0.4.
See all versions of @readystack/webfont-license-audit for other recorded verdicts.
- Review the evidence and your use of @readystack/webfont-license-audit@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.