@readystack/mssql-container-licence-lint
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
This report shows the evidence for @readystack/mssql-container-licence-lint@1.0.2. 0 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package performs undisclosed runtime telemetry when the CLI is used interactively, which warrants a warning under the review rules. The inspected telemetry contains usage fields only, and the license-key requests serve the package’s licensing function.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI for a free scan, or checking a paid feature without a license key, in an interactive terminal.
Impact
The vendor can observe product usage and whether the user encountered the paywall; no sensitive project or credential data was identified in these payloads.
Mechanism
The CLI posts product slug, source, and event reason to getreadystack.com/api/ev. Environment-variable opt-outs are present in the source.
AI rationale
The package performs undisclosed runtime telemetry when the CLI is used interactively, which warrants a warning under the review rules. The inspected telemetry contains usage fields only, and the license-key requests serve the package’s licensing function.
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 automatically calls `pingUse()` after scanning.
- `pingUse()` sends a usage event containing the product slug, CLI source, and `free` reason to `getreadystack.com/api/ev`; it has environment-variable opt-outs and only runs in a TTY.
- When no license key is available, `ensure()` calls `pingPaywall('no_key')`; that sends a paywall event with the product slug, source, and reason to the same endpoint.
Evidence against
- The manifest has no install lifecycle scripts; network behavior is triggered by running the CLI.
- The telemetry payloads contain usage fields rather than credentials, file contents, project details, or environment values.
- License keys are used for licensing validation, and the README describes the license requirement for paid workspace scans.
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...
...
L33: 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...
...
L33
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.2.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/mssql-container-licence-lint@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.