@iflyrpa/actions@4.1.2
@iflyrpa/playwright 包中发布逻辑的具体实现
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found no lifecycle hook or concrete malicious behavior. Network reporting is action-triggered and restricted to package-defined hosts.
Decision evidence
public snapshot- The package exposes library entrypoints and its scripts contain only build and development commands, with no install lifecycle hook.
- The bundled reporting function returns when no caller token is supplied and selects only one of two fixed service hosts before sending a publish log.
- The reporting function is invoked after a publish operation with caller-provided publish parameters.
- The bundle contains post-publish telemetry and a fixed error-webhook endpoint, but the inspected reporting destination is package-fixed and activation follows an invoked action.
Source & flagged code
4 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/bundle.jsView on unpkg · L9716Source fingerprint signature matches a known malicious package signature; route for source-aware review.
dist/bundle.jsView on unpkgPackage source references a known benign dynamic code generation pattern.
dist/bundle.jsView on unpkg · L11818Findings
Affected versions and remediation
This report applies to @iflyrpa/actions@4.1.2.
See all versions of @iflyrpa/actions for other recorded verdicts.
- Review the evidence and your use of @iflyrpa/actions@4.1.2 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.