portomatic@0.2.15
Slack for testing bots, with the real Slack client.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reviewed behavior fits a Slack bot testing package: child processes are started through an explicit helper, runtime telemetry is disclosed with an opt-out, and the CLI updater targets the package's configured release origin. The scanner's command-output and network flags reflect testing and product functions, not an identified exfiltration path.
Decision evidence
public snapshot- The manifest describes a Slack bot testing tool and exposes a CLI plus a Slack testing-library entry point.
- The testing library starts a child process only when its startBot method is called with an explicit command.
- Telemetry discloses its usage-metadata collection and supports opt-out; the package documentation states that message content, tokens, and payloads are not sent.
- The CLI updater uses the package's release origin and supports PORTOMATIC_NO_UPDATE; it is separate from the package's import entry point.
- The CLI checks for a release update when invoked and may download the selected runtime.
- The emulator sends runtime telemetry to the Portomatic telemetry service unless disabled.
- Starting the CLI's emulator may contact the Portomatic relay to enable sharing.
Source & flagged code
7 flaggedPackage source references child process execution.
products/slack/dist/src/cli/start.jsView on unpkg · L1Package source references dynamic require/import behavior.
products/slack/dist/src/main.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to portomatic@0.2.15.
See all versions of portomatic for other recorded verdicts.
- Review the evidence and your use of portomatic@0.2.15 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.