@lightupai/polaris@0.0.123
⚠ Under reviewRecord and stream Claude Code sessions to Slack. Like Gong for AI coding — capture every prompt, response, and tool call. Multiplayer collaboration across AI coding agents.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe readable manifest and scripts show no install hook, and the flagged package-manager use belongs to a manually invoked audit utility. The declared CLI source contains NUL bytes and remains materially unresolved, so the package cannot be cleared or blocked from the inspected evidence.
Decision evidence
public snapshot- The manifest maps the polaris command to bin/polaris and declares only a test script; it has no install lifecycle hook.
- The polaris wrapper executes src/cli/cli.ts, but that file could not be inspected because it contains NUL bytes.
- The performance audit is documented as a manually run command; its package-manager invocation is conditional on local auditing.
- No attack was confirmed in the readable source inspected.
Source & flagged code
6 flaggedPackage source references child process execution.
scripts/perf-audit.tsView on unpkg · L14A single source file combines environment access, network access, and code or shell execution; review context before blocking.
scripts/perf-audit.tsView on unpkg · L33Findings
Affected versions and remediation
This report applies to @lightupai/polaris@0.0.123.
See all versions of @lightupai/polaris for other recorded verdicts.
- Review the evidence and your use of @lightupai/polaris@0.0.123 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.