@pisell/pisellos@2.3.146
一个可扩展的前端模块化SDK框架,支持插件系统
AI Security Review
scanned 23d ago · by lpm-firewall-aiStatic inspection establishes automatic forwarding of an existing token to an unrestricted caller-selected endpoint. The evidence supports a dangerous-capability warning rather than a malicious-package block.
Decision evidence
public snapshot- The public entrypoint exports the request plugin through the plugin index.
- When initialized with a core and no authorization header, the request plugin automatically reads the existing token from window storage.
- The request destination comes from caller options without a destination allowlist in the inspected request flow.
- The request method passes this configuration to the fetch implementation, which sends the copied authorization header.
- No registry-install lifecycle hook or runtime self-dependency appears in package.json.
- No covert package-controlled credential recipient was established; exposure depends on the caller's request destination.
Source & flagged code
5 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/plugins/window.jsView on unpkgPackage source references a known benign dynamic code generation pattern.
dist/plugins/window.jsView on unpkg · L248Findings
Affected versions and remediation
This report applies to @pisell/pisellos@2.3.146.
See all versions of @pisell/pisellos for other recorded verdicts.
- Review the evidence and your use of @pisell/pisellos@2.3.146 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.