@ory/continue@1.8.1
Ory plugin for Continue CLI (cn): scaffolding skills, a local Ory instance, and authentication, authorization, and audit for every tool call
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package enables install-time analytics by default, and the payload includes an identifier read from the installer's Git configuration. This fits the warning-only telemetry category: the collector excludes the full email address, paths, and environment variables.
Decision evidence
public snapshot- The package depends on reova and sets its install analytics to enabled with endpoint https://telemetry.reo.dev/data.
- reova declares a postinstall script that runs its tracker.
- The postinstall tracker collects and sends analytics for dependent packages when analytics are enabled and an endpoint is configured.
- The install payload includes package details and system information such as platform, architecture, Node version, OS release, and CPU count.
- The collector reads the Git email from ~/.gitconfig and adds its domain to the payload as an organizational signal.
- The sender makes an HTTP POST to the configured endpoint.
- The collector sends only the Git email domain, not the full address.
- The documented payload excludes environment variables, file paths, and the dependency list.
Source & flagged code
7 flaggedSource fingerprint signature matches a known malicious package signature; route for source-aware review.
dist/cli/main.jsView on unpkgThe package depends on reova and sets its install analytics to enabled with endpoint https://telemetry.reo.dev/data.
package.jsonView on unpkg · L50Findings
Affected versions and remediation
This report applies to @ory/continue@1.8.1.
See all versions of @ory/continue for other recorded verdicts.
- Review the evidence and your use of @ory/continue@1.8.1 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.