@ory/amp@1.0.1
Ory plugin for Amp (Sourcegraph's coding agent): a permission delegate that authorizes every tool call plus an in-process plugin for session auth and activity auditing
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no automatic npm lifecycle trigger, but its explicit setup command configures broad agent interception and activity handling. This is a real, user-invoked agent capability rather than evidence of covert malware.
Static reason
No blocking static signals were detected.
Trigger
A user runs ory-amp install, ory-amp setup, or the setup binary.
Impact
The configured Ory runtime can mediate every Amp tool call and receive tool input and output data.
Mechanism
Agent configuration mutation and tool activity interception.
AI rationale
The package has no automatic npm lifecycle trigger, but its explicit setup command configures broad agent interception and activity handling. This is a real, user-invoked agent capability rather than evidence of covert malware.
Evidence
dist/cli/setup.jsdist/plugin.js~/.config/amp/settings.json.amp/plugins/ory.ts.agents/skills
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- Its explicit setup command adds a global Amp delegate for every tool call.
- The installed plugin receives tool inputs and results, then passes them to the Ory client.
- Setup writes an Amp plugin loader and project skill files.
Evidence against
- package.json defines no npm install lifecycle hook.
- The configuration changes occur only through declared CLI install or setup commands.
- No source in this package uses shell execution, eval, or direct secret harvesting.
Behavioral surface
EnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
2 flagged · loading sourcedist/cli/setup.jsView file
•Manifest-trigger-reachable source links an external AI-agent control path to a behavior-bearing write operation.
nst to = typeof rec.to === "string" ? rec.to : "";
return to === "ory-amp-permission" || /ory-hook-amp\.(js|cjs|mjs)$/.test(to);
}
function mergepermissions(existing, to) {
const merged = { ...existing };
const perms = (array.isarray(merged["amp.permissions"])
? merged["amp.permissions"]
: []).filter((e) => !isorydelegate(e));
perms.push(delegateentry(to));
merged["amp.permissions"] = perms;
return merged;
}
function removepermissions(existing) {
const merged = { ...existing };
High
Trigger Reachable External Ai Agent Control Surface Mutation
Manifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
dist/cli/setup.jsView on unpkg103* The `amp.permissions` delegate entry that routes every tool ("*") through
* the Ory permission helper. Amp invokes the named program with the tool
* params on stdin and reads the decision from the exit code.
*
* Verified against the binary: a flat top-level `amp.permissions` array of
* `{ tool, action, to }` entries, and `to` accepts an **absolute path** — its
* help text says the helper "must be on $PATH", but a path works and is what
* we write. That matters beyond consistency: a bare bin name only resolves
* from a shell-initialized PATH, which a GUI-launched Amp does not have.
Medium
Ai Review Evidence
Findings
1 High2 Medium4 Low
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/cli/setup.js
MediumEnvironment Vars
MediumAi Review Evidencedist/cli/setup.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @ory/amp@1.0.1.
See all versions of @ory/amp for other recorded verdicts.
- Review the evidence and your use of @ory/amp@1.0.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.