@readystack/swift6-concurrency-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.
11 rules that name the .swift lines Swift 6 language mode rejects — 13 findings, 6 build-blocking, on the 47-line fixture
This report shows the evidence for @readystack/swift6-concurrency-lint@1.0.5. 0 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends undisclosed runtime usage telemetry on interactive free runs, which warrants a warning under the review rules. The event contains only basic usage fields, is gated and opt-out, and no credential theft or other attack behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
After a free scan when the CLI is run with an interactive TTY.
Impact
The publisher can count interactive usage; the event does not include scanned files or credentials.
Mechanism
The CLI posts a small event with the tool slug, CLI source and free-run reason to the publisher's event endpoint. Environment-variable opt-outs and CI checks suppress it.
AI rationale
The CLI sends undisclosed runtime usage telemetry on interactive free runs, which warrants a warning under the review rules. The event contains only basic usage fields, is gated and opt-out, and no credential theft or other attack behavior was identified.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/swift6-concurrency-lint.json
Network endpoints3
getreadystack.com/api/evgetreadystack.com/api/licgetreadystack.com/api/rules/
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- After a free CLI run, the program calls `pingUse()`.
- The ping sends a usage event containing the tool slug, CLI source and `free` reason to `getreadystack.com/api/ev`; it is gated on an interactive TTY and can be disabled with environment variables.
- The README documents installation and CLI features but does not disclose this usage telemetry.
Evidence against
- The usage event contains no file contents, credentials, hostname or username.
- Telemetry is limited to interactive runs and can be disabled with `DO_NOT_TRACK=1` or `READYSTACK_NO_TELEMETRY`; CI runs are excluded.
- License validation and rule-feed requests send the package's own license key to the package's licensing host. This is consistent with the documented licensed feature.
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 = '';
...
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: true }); });
L34: req.end();
L35: })
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 = '';
...
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 () { reso
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/swift6-concurrency-lint@1.0.5.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @readystack/swift6-concurrency-lint@1.0.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.