prismic@1.18.0
Prismic's official command line tool
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection shows a user-invoked Prismic CLI with no registry install hook, no self-dependency chain, and credentials used for the Prismic host stored with the session. Agent detection and telemetry are product behavior and do not write a foreign agent control surface.
Decision evidence
public snapshot- package.json exposes only the prismic CLI bin at dist/index.mjs, ships dist, and has a prepare build script with no preinstall, install, or postinstall hook and no runtime dependencies.
- Authentication defaults the service host to prismic.io, stores the session token in the user config directory, and refreshes it against https://auth.${host} only when the CLI runs.
- dist/index.mjs is a user-invoked Node CLI; detected agent environment variables only mark analytics options, and the package does not write agent control files.
- The CLI sends product telemetry to api.segment.io and a Sentry DSN, and can spawn a detached helper or a local open command, all after the user runs the CLI.
Source & flagged code
6 flaggedPackage name is suspiciously similar to a popular package name.
package.jsonView on unpkgPackage source references child process execution.
dist/auth-BQ-T06tR.mjsView on unpkg · L1Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
Findings
Affected versions and remediation
This report applies to prismic@1.18.0.
See all versions of prismic for other recorded verdicts.
- Review the evidence and your use of prismic@1.18.0 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.