@pisell/pisellos@2.3.167
一个可扩展的前端模块化SDK框架,支持插件系统
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found a build-only prepublish hook and configurable logging whose default Feishu destination is an unusable placeholder. The scanner’s network, logging, and dynamic-code indicators do not establish an active attack in the inspected paths.
Decision evidence
public snapshot- The package entrypoint is dist/index.js, and its only npm lifecycle hook is prepublishOnly running a build.
- The request plugin sends requests to the URL supplied in request configuration; no credential collection or unrelated recipient is shown in the inspected path.
- ScanOrder logs include its cache identifier and payload only when a logger is present; otherwise error logs go to the local console.
- The logger defaults to Feishu with a placeholder webhook, rejects placeholder webhooks, and takes logger configuration from application options.
- The flagged registration utilities format and mask email addresses; the window timer uses the platform timer when available and evaluates a supplied string handler only in its fallback.
- The logger supports POSTing application log records to configured Feishu or Grafana destinations, and the window timer has a fallback that evaluates string handlers.
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.167.
See all versions of @pisell/pisellos for other recorded verdicts.
- Review the evidence and your use of @pisell/pisellos@2.3.167 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.