@readystack/swift6-concurrency-lint@1.0.4
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
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe runtime telemetry is limited and opt-out capable, but it is not disclosed in the README. Under the review rules, undisclosed runtime telemetry is suspicious; no credential exfiltration or unrelated collection was identified.
Decision evidence
public snapshot- The CLI calls `pingUse()` after a free run completes.
- The usage event sends only event type, package slug, source, and reason to `getreadystack.com`.
- Usage and paywall telemetry are gated to interactive use and can be disabled with `DO_NOT_TRACK=1` or `READYSTACK_NO_TELEMETRY`; CI is excluded.
- The rule feed is fetched only when a license key is present, from the vendor domain, with the key used to retrieve product rules.
- The README describes the linting and license features but does not disclose the runtime usage telemetry.
- The telemetry payload does not include credentials, project files, paths, or other environment values.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @readystack/swift6-concurrency-lint@1.0.4.
See all versions of @readystack/swift6-concurrency-lint for other recorded verdicts.
- Review the evidence and your use of @readystack/swift6-concurrency-lint@1.0.4 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.