@readystack/nuget-commercial-license-gate
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.
Flags AutoMapper 15+, MediatR 13+, FluentAssertions 8+, MassTransit 9+ and other NuGet versions past their licence line, with the pin
This report shows the evidence for @readystack/nuget-commercial-license-gate@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 reported credential flow is license-key validation to the package's licensing services, not unrelated credential collection. The CLI also sends undisclosed, minimal runtime usage telemetry by default in interactive sessions, which warrants a warning.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A free CLI run completes in a terminal, or a paywall check runs in an interactive terminal or MCP session.
Impact
The vendor can count interactive usage and paywall events; the observed payloads do not contain identifying details or user data.
Mechanism
The CLI posts a usage or paywall event with the package slug, source, and fixed reason to getreadystack.com. Telemetry can be disabled with DO_NOT_TRACK=1, READYSTACK_NO_TELEMETRY, or CI.
AI rationale
The reported credential flow is license-key validation to the package's licensing services, not unrelated credential collection. The CLI also sends undisclosed, minimal runtime usage telemetry by default in interactive sessions, which warrants a warning.
Evidence
license.jscli.js$READYSTACK_HOME/nuget-commercial-license-gate.json~/.config/readystack/nuget-commercial-license-gate.json
Network endpoints4
getreadystack.com/api/evgetreadystack.com/api/lic?key=...getreadystack.com/api/rules/<slug>?key=...api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- A free CLI run sends a usage event containing only the package slug, CLI source, and a fixed reason.
- Paywall telemetry is limited to interactive terminal or MCP sessions and can be disabled with environment flags.
- The license key is sent to the package vendor and Polar for license validation.
Evidence against
- The manifest has no install lifecycle scripts; the CLI runs when invoked.
- The telemetry payloads do not include hostnames, usernames, project paths, file contents, or credentials.
- The scanner's credential concern is explained by license-key validation and the key-gated rules feed.
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...
...
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/nuget-commercial-license-gate@1.0.2.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/nuget-commercial-license-gate@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.