registry / @readystack/cron-schedule-lint / 0.1.9
@readystack/cron-schedule-lint@0.1.9
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.
Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at all - and prints the next three times each one really fires, in the zone that actually applies.
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found no lifecycle hooks or concrete malicious behavior. Network activity is tied to licensing, optional rule retrieval, and limited usage events; the observed license key transfer is to the package's licensing service.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the CLI activates its scan; paid features may validate a supplied or stored license, and an interactive free run may send a usage event.
Impact
No confirmed attack behavior was found. The inspected source does not establish arbitrary execution, persistence, destructive actions, or consumer policy changes.
Mechanism
License keys go to license validation endpoints. Usage events send product and event labels; no credential or file-content transfer was identified in those events.
AI rationale
Source inspection found no lifecycle hooks or concrete malicious behavior. Network activity is tied to licensing, optional rule retrieval, and limited usage events; the observed license key transfer is to the package's licensing service.
Evidence
package.jsoncli.jslicense.js
Network endpoints4
getreadystack.com/api/licapi.polar.sh/v1/customer-portal/license-keys/validategetreadystack.com/api/rules/getreadystack.com/api/ev
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes cli.js as the executable and contains no lifecycle script.
- The CLI scans supplied text with configured rules; it does not execute the matched content.
- License keys are sent to the package's licensing service and Polar's license validation endpoint.
- Usage events contain a tool label and use reason; the CLI gates its event on an interactive terminal, while license events also honor CI and telemetry opt-outs.
- The CLI loads optional rule data through the license helper; inspection found no payload execution path.
Evidence against
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
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/cron-schedule-lint@0.1.9.
See all versions of @readystack/cron-schedule-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/cron-schedule-lint@0.1.9 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.