@readystack/gnu-global-cpp-vscode-config-pack@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.
21 rules that read the values in a shared .vscode folder, plus 45 snippets. VS Code loads a wrong value without a word - this names the line and the fix.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s purpose is a VS Code configuration scanner, and the license key traffic is tied to its own licensing and rule-feed services. However, free interactive CLI runs send usage telemetry to the vendor without user-facing disclosure, so this is suspicious rather than malicious.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI on files without paid options in an interactive terminal.
Impact
The vendor learns that the package was used in an interactive session; no project or credential data is included in this event.
Mechanism
The CLI posts a usage event containing the product slug, CLI source, and fixed reason to the vendor endpoint. Environment-variable and CI guards can disable or skip the request.
AI rationale
The package’s purpose is a VS Code configuration scanner, and the license key traffic is tied to its own licensing and rule-feed services. However, free interactive CLI runs send usage telemetry to the vendor without user-facing disclosure, so this is suspicious rather than malicious.
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
- The package is a CLI for scanning VS Code configuration files with rules.
- After a free CLI run, the code automatically calls its usage-reporting function.
- The usage event sends only the package slug, CLI source, and fixed reason to getreadystack.com/api/ev.
- The usage event is limited to interactive runs and is skipped for CI or when DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY is set.
- The license key is used for product license validation and the vendor’s rule feed; no unrelated credential source or destination appeared in the inspected paths.
Evidence against
- The reported usage fields contain no project files, paths, usernames, or environment values.
- The usage event is opt-out and does not run in CI or non-interactive sessions.
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/gnu-global-cpp-vscode-config-pack@0.1.5.
See all versions of @readystack/gnu-global-cpp-vscode-config-pack for other recorded verdicts.
- Review the evidence and your use of @readystack/gnu-global-cpp-vscode-config-pack@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.