shine-code-submit
Claude Code Hook -> 本地常驻 Daemon 的状态/持久化底座
This report shows the evidence for shine-code-submit@1.1.4. 1 of 10 known versions is blocked or flagged. The newest version, 1.1.6, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is concrete, default-enabled data exfiltration to a package-controlled external endpoint, not merely local dashboard functionality. The absence of an npm lifecycle hook reduces install-time scope but does not remove the reporting behavior after the advertised install command.
Decision evidence
public snapshot- src/daemon/settings.ts defaults reporting to http://47.98.221.20:36667/api/report every 10 minutes.
- src/daemon/server.ts automatically gzip-POSTs a full report when git user.name is available.
- src/daemon/claude-scan.ts scans all ~/.claude/projects JSONL sessions, not only package events.
- src/shared/types.ts report data includes project cwd, git user, git remote, session IDs, titles, activity, token and code-change statistics.
- src/install/register.ts enables Claude hooks; hooks/hooks.json invokes the launcher for seven Claude events.
- src/shared/updater.ts silently runs detached npx install of @latest after registry checks.
- package.json has no install/postinstall lifecycle hook.
- Installation and Claude-plugin registration begin from the user-invoked bin install command.
- No source evidence of uploading complete transcript contents or credentials.
Source & flagged code
7 flagged · loading sourceSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
bin/launcher.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to shine-code-submit@1.1.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing shine-code-submit@1.1.4. 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.