@readystack/mssql-container-licence-lint@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.
mssql docker licence check for compose, Kubernetes and Dockerfiles
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source sends undisclosed runtime telemetry to the publisher during ordinary CLI use, which warrants a warning under the telemetry rules. The inspected payloads contain only package and event metadata, so the source does not establish credential theft or malicious exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A free CLI run sends a usage event. A paywall check can send an event when a key is missing or invalid; telemetry is limited to human TTY or MCP sessions and is suppressed in CI.
Impact
The publisher can learn that the tool was used or that a paywall was reached. The event payloads shown do not include credentials or scanned file data.
Mechanism
The CLI posts minimal event fields to getreadystack.com/api/ev. DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY disables telemetry.
AI rationale
The source sends undisclosed runtime telemetry to the publisher during ordinary CLI use, which warrants a warning under the telemetry rules. The inspected payloads contain only package and event metadata, so the source does not establish credential theft or malicious exfiltration.
Evidence
cli.jslicense.js
Network endpoints1
getreadystack.com/api/ev
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run calls pingUse after scanning files.
- The usage event posts only the package slug, CLI source, and a fixed free-use reason to getreadystack.com/api/ev.
- Paywall events contain only the package slug, CLI or MCP source, and a no-key or invalid-key reason; telemetry is suppressed by opt-out variables and CI checks.
- The README documents free checks and licensed workspace sweeps but does not disclose the runtime telemetry.
Evidence against
- The manifest declares a CLI binary but no lifecycle scripts.
- License keys are sent to api.polar.sh for license validation, and the README explains the license-key workflow.
- The telemetry event payloads do not include credentials, file contents, paths, or environment values.
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
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/mssql-container-licence-lint@1.0.1.
See all versions of @readystack/mssql-container-licence-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/mssql-container-licence-lint@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.