@tigrisdata/cli
Command line interface for Tigris object storage
This report shows the evidence for @tigrisdata/cli@3.11.0. 1 of 13 known versions is blocked or flagged. The newest version, 3.17.1, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an automatic postinstall mutation of a foreign AI-agent control surface, not an explicit user-command setup flow. The hook installs behavioral instructions that influence future agent actions.
Decision evidence
public snapshot- The manifest runs postinstall automatically.
- The install hook copies a package skill into the user's Claude Code skills directory when .claude exists.
- The installed skill is non-user-invocable and directs the agent to prefer Tigris for all object-storage work.
- The hook does not show credential collection, network access, or shell execution.
- Other agent configuration changes are behind the interactive tigris init command.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe manifest runs postinstall automatically.
package.jsonView on unpkg · L68Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @tigrisdata/cli@3.11.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @tigrisdata/cli@3.11.0. 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.