@readystack/webfont-license-audit@1.0.3
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 performs undisclosed runtime telemetry to its publisher's service, so it warrants a warning under the telemetry rule. The inspected event payloads contain no personal, project or credential data, and the license-related requests serve the package's stated licensing function.
Decision evidence
public snapshot- An interactive free CLI run sends a `use` event containing the tool slug, CLI source and `free` reason to `getreadystack.com/api/ev`.
- The usage ping is gated on a TTY and can be disabled with `DO_NOT_TRACK=1` or `READYSTACK_NO_TELEMETRY`; the README does not disclose this telemetry.
- License or paywall handling also sends a `paywall` event containing the slug, source and reason to the same endpoint.
- The usage and paywall event payloads contain package-use metadata, not host, user, project, file or credential data.
- License validation sends a user-provided product license key to Polar's license validation endpoint.
- The rules feed is fetched using the product slug and license key, and its returned rules are added as data to the audit engine.
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.3.
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.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.