@readystack/impressum-lint-de@1.0.5
Not affiliated with ReadyStack (readystack.dev). No new versions are published here.
17 Regeln mit Stichtag für Impressum, Footer und Shop-Templates im Repository
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI automatically sends the user's Polar license key to getreadystack.com on startup, including before argument handling. This is credential exfiltration to a host other than the credential's service.
Decision evidence
public snapshot- The CLI calls lic.pullFeed() at startup before parsing arguments, so the request runs whenever the command starts.
- pullFeed reads READYSTACK_LICENSE or a stored key from the package's license state.
- The key is appended to a request sent to getreadystack.com.
- The package is an Impressum linter, and the feed is described as delivering updated lint rules to licensed users.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
license.jsView on unpkg · L2Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
license.jsView on unpkg · L2A manifest entrypoint or package-local install chain reaches credential exfiltration behavior.
license.jsView on unpkg · L2This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to @readystack/impressum-lint-de@1.0.5.
See all versions of @readystack/impressum-lint-de for other recorded verdicts.
- Avoid installing @readystack/impressum-lint-de@1.0.5. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.