registry / Telemetry / @readystack/streitbeilegung-hinweis-lint

@readystack/streitbeilegung-hinweis-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.

Findet den seit 20.07.2025 toten OS-Plattform-Link, Zitate der aufgehobenen ODR-VO (VO (EU) 2024/3228) und fehlende Hinweise nach § 36 VSBG in Impressum, AGB und Footer.

This report shows the evidence for @readystack/streitbeilegung-hinweis-lint@1.0.3. 0 of 3 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 4d ago · by lpm-firewall-ai

The default interactive usage ping is runtime telemetry without user-facing disclosure, so this is suspicious rather than malicious. The reported credential flow sends the package’s own license key to its own service for validation and feed access.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

A user runs a free scan in an interactive terminal or session.

Impact

The vendor learns that the tool was used, with the event source and reason; no credential or scanned file content is included in this event.

Mechanism

The CLI sends a POST with fixed event fields to getreadystack.com/api/ev; CI and explicit telemetry opt-outs suppress it.

AI rationale

Evidence

cli.js

Network endpoints1

getreadystack.com/api/ev

Decision evidence

public snapshot

AI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

Interactive free scans send a fixed usage event containing the package slug, CLI source, and event reason to getreadystack.com.
The usage ping runs automatically after a free scan; it is limited to interactive sessions and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.

Evidence against

License keys are sent to getreadystack.com for license validation and the package’s own rules feed, which are features described by the package.

Behavioral surface

Source

EnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

Manifest

NoLicense

scanned 3 file(s), 25.4 KB of source, external domains: getreadystack.com

Source & flagged code

5 flagged

license.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 · L2

2Trigger-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/streitbeilegung-hinweis-lint@1.0.3.

The versions list below shows the verdict for each recorded version.

Review the evidence and your use of @readystack/streitbeilegung-hinweis-lint@1.0.3 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: 2026-10-31 17:38:38.265Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

3 known versions

1.0.3latestshownSuspiciousTelemetryWarnPublishedSep 29, 2026, 1:45 PM 1.0.2SuspiciousTelemetryWarnPublishedSep 28, 2026, 2:02 PM 1.0.1Clean—AllowPublishedSep 26, 2026, 4:17 AM

registry / Telemetry / @readystack/streitbeilegung-hinweis-lint

@readystack/streitbeilegung-hinweis-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.

Findet den seit 20.07.2025 toten OS-Plattform-Link, Zitate der aufgehobenen ODR-VO (VO (EU) 2024/3228) und fehlende Hinweise nach § 36 VSBG in Impressum, AGB und Footer.

This report shows the evidence for @readystack/streitbeilegung-hinweis-lint@1.0.3. 0 of 3 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 4d ago · by lpm-firewall-ai

Static reason

High-risk behavior combination matched malicious policy.

Trigger

A user runs a free scan in an interactive terminal or session.

Impact

The vendor learns that the tool was used, with the event source and reason; no credential or scanned file content is included in this event.

Mechanism

The CLI sends a POST with fixed event fields to getreadystack.com/api/ev; CI and explicit telemetry opt-outs suppress it.

AI rationale

Evidence

cli.js

Network endpoints1

getreadystack.com/api/ev

Decision evidence

public snapshot

AI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

Interactive free scans send a fixed usage event containing the package slug, CLI source, and event reason to getreadystack.com.
The usage ping runs automatically after a free scan; it is limited to interactive sessions and can be disabled with DO_NOT_TRACK=1 or READYSTACK_NO_TELEMETRY.

Evidence against

License keys are sent to getreadystack.com for license validation and the package’s own rules feed, which are features described by the package.

Behavioral surface

Source

EnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

Manifest

NoLicense

scanned 3 file(s), 25.4 KB of source, external domains: getreadystack.com

Source & flagged code

5 flagged

license.jsView file

Critical

Credential Exfiltration

Source appears to send environment or credential material to an external endpoint.

license.jsView on unpkg · L2

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/streitbeilegung-hinweis-lint@1.0.3.

The versions list below shows the verdict for each recorded version.

Review the evidence and your use of @readystack/streitbeilegung-hinweis-lint@1.0.3 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: 2026-10-31 17:38:38.265Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

3 known versions

1.0.3latestshownSuspiciousTelemetryWarnPublishedSep 29, 2026, 1:45 PM 1.0.2SuspiciousTelemetryWarnPublishedSep 28, 2026, 2:02 PM 1.0.1Clean—AllowPublishedSep 26, 2026, 4:17 AM

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

More from @readystack

Runtime surface

Behavioral surface

Related packages

More from @readystack