registry / @lightupai/polaris / 0.0.106
@lightupai/polaris@0.0.106
⚠ 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 source supports ordinary Slack reporting and bridging, and the manifest shows no install hook. The CLI launcher reaches an unreadable implementation, so its behavior remains unresolved and warrants manual review.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the polaris CLI launcher.
Impact
The unresolved CLI behavior prevents a confident clean determination.
Mechanism
The launcher runs src/cli/cli.ts, but that file could not be read because it contains NUL bytes.
AI rationale
The readable source supports ordinary Slack reporting and bridging, and the manifest shows no install hook. The CLI launcher reaches an unreadable implementation, so its behavior remains unresolved and warrants manual review.
Evidence
package.jsonbin/polarissrc/cli/cli.ts
Decision evidence
public snapshotAI called this Manual Review at 96.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json declares CLI binaries and no install lifecycle hook; its only script is a test command.
- The polaris launcher dispatches to src/cli/cli.ts, whose contents could not be read because it contains NUL bytes.
- Inspected web and Slack bridge code sends signup and project event data to Slack as part of the package’s stated product behavior.
Evidence against
- The CLI implementation remains unresolved, so the inspected launcher and other source files do not establish that the package is clean.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
NoLicenseWildcardDependency
Source & flagged code
6 flaggedscripts/perf-audit.tsView file
14import { mkdirSync, writeFileSync } from "fs";
L15: import { execSync } from "child_process";
L16: import { join } from "path";
High
Child Process
Package source references child process execution.
scripts/perf-audit.tsView on unpkg · L1433console.log(" Building CSS and starting local server ...");
L34: execSync("npx bun x tailwindcss -i src/web/styles/input.css -o src/web/styles/output.css --minify", { stdio: "pipe" });
L35:
L36: const port = await freePort();
L37: url = `http://localhost:${port}`;
L38:
L39: const proc = Bun.spawn(["bun", "run", "src/web/serve.ts"], {
L40: env: { ...process.env, WEB_PORT: String(port), DATABASE_URL: process.env.DATABASE_URL ?? "postgres://polaris:polaris@localhost:5432/polaris" },
L41: stdout: "pipe",
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
scripts/perf-audit.tsView on unpkg · L3333console.log(" Building CSS and starting local server ...");
L34: execSync("npx bun x tailwindcss -i src/web/styles/input.css -o src/web/styles/output.css --minify", { stdio: "pipe" });
L35:
Findings
1 Critical5 High5 Medium5 Low
CriticalCredential Exfiltrationsrc/web/app.ts
HighChild Processscripts/perf-audit.ts
HighShell
HighSame File Env Network Executionscripts/perf-audit.ts
HighRuntime Package Installscripts/perf-audit.ts
HighSemantic Analysis Limitedbin/polaris
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperdocker/bridge-entrypoint.sh
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @lightupai/polaris@0.0.106.
See all versions of @lightupai/polaris for other recorded verdicts.
- Review the evidence and your use of @lightupai/polaris@0.0.106 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.