registry / minimal-forge-work-pack-sync / 0.1.34
minimal-forge-work-pack-sync@0.1.34
Minimal Forge Work Pack startup synchronization for OpenCode and OpenWork.
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection found no lifecycle hook and no credential transfer to an unrelated recipient. The credential lookup, endpoint restrictions, and limited usage payload align with the package's configured Forge synchronization behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
OpenCode loads and invokes the configured plugin; usage reporting follows an invocation of a Forge-managed skill.
Impact
No unrelated credential disclosure or other confirmed attack effect was found.
Mechanism
The plugin reads credentials associated with its configured Forge origin, validates that origin, and sends sync or usage requests there. Usage events contain work-pack metadata rather than prompt text.
AI rationale
Source inspection found no lifecycle hook and no credential transfer to an unrelated recipient. The credential lookup, endpoint restrictions, and limited usage payload align with the package's configured Forge synchronization behavior.
Evidence
package.jsondist/index.js
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies a startup synchronization plugin and exposes dist/index.js as its entrypoint; it has no lifecycle script.
- The plugin requires a configured Forge origin and starts its synchronization through that plugin entrypoint.
- Credentials are retrieved from the OpenCode auth entry keyed by that same Forge origin.
- The configured origin must use HTTPS, except for loopback, and cannot include credentials or a path.
- Usage reports are limited to managed skill invocations and contain the skill slug, day, and count.
- Usage events are sent to the configured Forge origin's evidence route; no unrelated credential recipient was identified.
Evidence against
Behavioral surface
CryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
4 flaggeddist/index.jsView file
2615if (typeof node_buffer.Buffer === "function") {
L2616: return node_buffer.Buffer.from(src, "base64");
L2617: } else if (typeof atob === "function") {
...
L5229: yield* this.next(token);
L5230: yield* this.end(forceDoc, endOffset);
L5231: }
...
L5233: *next(token) {
L5234: if (node_process.env.LOG_STREAM)
L5235: console.dir(token, { depth: null });
...
L7670: const probe = async () => {
L7671: const response = await fetch(new URL(route, url2), { headers, signal: controller.signal, redirect: "error" });
L7672: if (!response.ok) return { status: "unknown" };
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L26152615Trigger-reachable chain: manifest.main -> dist/index.js
L2615: if (typeof node_buffer.Buffer === "function") {
L2616: return node_buffer.Buffer.from(src, "base64");
L2617: } else if (typeof atob === "function") {
...
L5229: yield* this.next(token);
L5230: yield* this.end(forceDoc, endOffset);
L5231: }
...
L5233: *next(token) {
L5234: if (node_process.env.LOG_STREAM)
L5235: console.dir(token, { depth: null });
...
L7670: const probe = async () => {
L7671: const response = await fetch(new URL(route, url2), { headers, signal: controller.signal, redirect: "error" });
L7672: if (!response.ok) return { status: "unknown" };
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsFindings
2 Critical1 High3 Medium6 Low
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to minimal-forge-work-pack-sync@0.1.34.
See all versions of minimal-forge-work-pack-sync for other recorded verdicts.
- Review the evidence and your use of minimal-forge-work-pack-sync@0.1.34 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.