@readystack/webfont-license-audit@1.0.2
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 to its vendor during interactive use, so this is a warning-level telemetry concern. The events contain only package and event metadata; licence validation and rule-feed requests send the package’s own licence key to its related services.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
An interactive free CLI run sends a usage event; a missing or invalid licence can also trigger a paywall event during an interactive CLI or MCP session.
Impact
The vendor learns that the package was used and whether a licence was missing or invalid, without consent being disclosed in the README.
Mechanism
POSTs package slug, event type, source, and reason to the vendor’s `/api/ev` endpoint. The event omits user and project identifiers and can be disabled with documented-in-code environment flags.
AI rationale
The package sends undisclosed runtime usage telemetry to its vendor during interactive use, so this is a warning-level telemetry concern. The events contain only package and event metadata; licence validation and rule-feed requests send the package’s own licence key to its related services.
Evidence
cli.jslicense.jsREADME.md
Network endpoints3
getreadystack.com/api/evgetreadystack.com/api/rules/<slug>?key=...api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- An interactive free CLI run sends a `use` event with the package slug, source, and reason to `getreadystack.com/api/ev`.
- The event is sent after a free run; telemetry is skipped when `DO_NOT_TRACK=1`, `READYSTACK_NO_TELEMETRY`, or `CI` is set, and when no TTY is present.
- The README describes CLI, MCP, and CI use but does not disclose this usage event.
- The licence key is sent to Polar for validation and to the package vendor’s rule-feed endpoint.
Evidence against
- The usage event contains no credentials, file contents, hostnames, usernames, or project paths.
- The usage event is gated to interactive CLI or MCP sessions and has opt-out environment variables.
- The manifest defines a CLI entrypoint and no lifecycle scripts; the inspected code’s network activity supports licensing, rule updates, and minimal usage counting.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
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.2.
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.2 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.