@apilift/cli@1.7.2
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged credential redirection and remote execution were not substantiated; credentials use an explicit setup flow and the operating system vault. However, runtime telemetry is sent by default when service settings enable it, and the package source does not clearly disclose that collection, so this merits a warning.
Decision evidence
public snapshot- After a counted CLI command, the package records its command, purpose, result, duration, and agent, then starts a background collector.
- Event properties are allowlisted; command events contain metadata rather than command arguments or output.
- When enabled by service-provided settings, queued events are sent to the analytics host with account, workspace, and installation IDs.
- The collector can be disabled with APILIFT_COLLECTOR_DISABLED=1, but it starts by default.
- No install lifecycle scripts are declared.
- Credential setup is an explicit command, and credentials are stored through the operating system credential vault.
- The reviewed credential and analytics flows did not substantiate the flagged remote execution or credential redirection.
Source & flagged code
6 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/apilift.jsView on unpkgFindings
Affected versions and remediation
This report applies to @apilift/cli@1.7.2.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.7.2 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.