@readystack/outlook-email-html-lint@0.1.5
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.
Classic Outlook renders with the Word engine, the new Outlook with WebView2. Lint one email file against both at once, line by line, before you send.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source sends runtime usage events to the publisher's service, and the README does not disclose this reporting. The events contain only the package slug, source, and reason, so this is undisclosed telemetry rather than data exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A free CLI scan, or a missing or invalid license check; MCP license checks can also report events.
Impact
The publisher can count package use and license-check outcomes. The observed payload does not include user files or credentials.
Mechanism
The package posts an event with the package slug, source, and reason to /api/ev. The event is gated by opt-out and CI checks, except MCP sessions bypass the interactive-terminal check.
AI rationale
The source sends runtime usage events to the publisher's service, and the README does not disclose this reporting. The events contain only the package slug, source, and reason, so this is undisclosed telemetry rather than data exfiltration.
Evidence
cli.jslicense.js
Network endpoints3
getreadystack.com/api/evgetreadystack.com/api/rules/api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The CLI sends a runtime usage event containing the package slug, source, and event reason to getreadystack.com.
- A normal free CLI run calls the usage telemetry function after scanning files.
- The package source allows telemetry to be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY, but the README does not describe this telemetry.
Evidence against
- The usage event contains no file contents, credentials, hostnames, or usernames.
- CLI usage telemetry is limited to interactive sessions and can be disabled; CI runs are excluded.
- License keys are sent to Polar's license validation endpoint, while the package's rules feed is fetched from the publisher's own domain.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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
3 Critical2 High3 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
CriticalPrevious Version Dangerous Deltacli.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/outlook-email-html-lint@0.1.5.
See all versions of @readystack/outlook-email-html-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/outlook-email-html-lint@0.1.5 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.