@readystack/webfont-license-audit@1.0.1
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 limited runtime telemetry without disclosing it in its README, which warrants a warning under the review rules. The observed events omit identifying or project data, and the license key is sent to the package vendor's own service.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI; telemetry events require an interactive terminal or MCP session, while the feed request runs at CLI startup when a key is available and its cache is stale.
Impact
The vendor receives basic usage details and the license key during feed refresh. No project content or unrelated credentials were found in these flows.
Mechanism
The CLI sends product-use or paywall events to getreadystack.com. The rules-feed GET request includes the configured license key in its URL query string.
AI rationale
The package performs limited runtime telemetry without disclosing it in its README, which warrants a warning under the review rules. The observed events omit identifying or project data, and the license key is sent to the package vendor's own service.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/webfont-license-audit.json (or the path under READYSTACK_HOME)
Network endpoints3
getreadystack.com/api/evgetreadystack.com/api/rules/<slug>?key=<license-key>api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI pulls the rules feed before parsing any command-line arguments; with a saved or environment license key, the feed request sends that key in a query parameter to getreadystack.com.
- Interactive runs send a usage or paywall event containing the package slug, source, and reason to getreadystack.com; the events are gated by terminal/session checks and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.
- The README describes the scanner and license features but does not disclose these telemetry requests.
Evidence against
- The telemetry payloads contain only the product slug, invocation source, and event reason; no hostname, username, project path, file contents, or other environment values are included.
- License validation and rule-feed requests go to the package vendor's service, and the feed is consumed as rule data by the scanner.
- Telemetry has opt-out environment variables and is restricted to interactive use; install scripts are absent.
Behavioral surface
EnvironmentVarsFilesystem
Source & flagged code
5 flaggedlicense.jsView file
2'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L31: req.on('error', function () { resolve({ ok: false, offline:
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L22Trigger-reachable chain: manifest.bin -> cli.js -> license.js
L2: 'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L31
Findings
2 Critical2 High4 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencecli.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/webfont-license-audit@1.0.1.
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.1 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.