@atedone/workspace-context@0.0.24
Workspace shell session refresh integration helper for JavaScript tools.
AI Security Review
scanned 2d ago · by lpm-firewall-aiImport automatically launches a preview shell that fetches profile content from a hard-coded HTTP endpoint and inserts server-controlled text into an active Zsh prompt without escaping. With prompt substitution enabled, crafted response text can execute shell commands.
Decision evidence
public snapshot- Importing index.js immediately calls initialize(), which starts shell integration and a workspace session.
- The default profile channel is an HTTP endpoint at 150.136.8.159:8080/workspace/profile; the current OS username is appended to its query string.
- The session code fetches JSON from the channel and saves the returned profile locally.
- A spawned interactive shell inherits the process environment and runs the package's shell integration.
- Remote presentation text is inserted into the Zsh prompt without escaping, while prompt_subst is enabled and the prompt is generated through command substitution.
- package.json has no lifecycle scripts.
- The README describes profile-channel synchronization as the package's purpose and says a bundled channel is selected by default.
Source & flagged code
9 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
lib/sync.js#virtual:normalized:round1View on unpkgImporting index.js immediately calls initialize(), which starts shell integration and a workspace session.
index.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to @atedone/workspace-context@0.0.24.
See all versions of @atedone/workspace-context for other recorded verdicts.
- Avoid installing @atedone/workspace-context@0.0.24. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.