@readystack/conda-channel-license-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.
Finds every environment.yml and .condarc line that pulls from Anaconda's licensed repository
This report shows the evidence for @readystack/conda-channel-license-lint@1.0.1. 0 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s scanner and license checks fit its stated purpose, and I found no credential or project-data exfiltration. However, interactive runs send undisclosed usage and paywall telemetry to the vendor, which warrants a warning.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running free checks in an interactive terminal, or reaching a missing or invalid license-key state; CI and configured telemetry opt-outs suppress the events.
Impact
The vendor can observe usage and license-prompt events. The inspected event payloads do not include credentials or scanned content.
Mechanism
The CLI posts event type, package slug, source, and reason to the vendor’s event endpoint. The README does not disclose this telemetry.
AI rationale
The package’s scanner and license checks fit its stated purpose, and I found no credential or project-data exfiltration. However, interactive runs send undisclosed usage and paywall telemetry to the vendor, which warrants a warning.
Evidence
license.jscli.js~/.config/readystack/conda-channel-license-lint.json (or the path under READYSTACK_HOME)
Network endpoints4
getreadystack.com/api/evgetreadystack.com/api/licgetreadystack.com/api/rules/api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- TTY-based free CLI runs send a use event containing the package slug, CLI source, and event reason to getreadystack.com/api/ev; the README does not disclose this telemetry.
- Missing or invalid license keys can send a similarly limited paywall event to the same endpoint; telemetry can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY, and is skipped in CI.
- License keys are sent to getreadystack.com and api.polar.sh for license validation, consistent with the package’s documented license feature.
- When a license key is configured or cached, CLI startup can send it to getreadystack.com to retrieve the package’s rules feed.
Evidence against
- The package describes itself as a Conda channel license linter, and its CLI entry point runs that scanner.
- The telemetry payloads contain event type, package slug, source, and reason; inspected code does not add credentials, file contents, or project data to those events.
- License validation and rules retrieval use the package vendor’s service and Polar’s license validation API.
Behavioral surface
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/conda-channel-license-lint@1.0.1.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/conda-channel-license-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.