@slowcook-ai/review-overlay
Floating review overlay for slowcook mock previews — element-anchored comments, screenshot, viewport metadata; submits to the mockup PR via PAT. Mounted into the mock app's root layout. Plate parses the comments back out for amendments.
This report shows the evidence for @slowcook-ai/review-overlay@0.25.7. 1 of 10 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe component silently sends a stored GitHub credential to the screen-time relay, which defaults to authBase, despite the README promising the PAT only goes to GitHub. The Trojan Source alert on comment-format.js was not confirmed as attack behavior.
Decision evidence
public snapshot- The screen-time relay defaults to the configured authBase.
- The relay receives the stored GitHub token in a Bearer header on a POST to /screentime.
- The component sends relay reports automatically during active review time and after successful issue filing.
- The README says the PAT only leaves the browser on direct fetches to GitHub's API.
- The package is designed to file review comments as GitHub issues, and its GitHub API requests send tokens to api.github.com.
- The relay host is configurable rather than a hard-coded collector.
- The package declares no install lifecycle scripts.
Source & flagged code
6 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/comment-format.jsView on unpkg · L242A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/comment-format.jsView on unpkgFindings
Affected versions and remediation
This report applies to @slowcook-ai/review-overlay@0.25.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing @slowcook-ai/review-overlay@0.25.7. 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.