event-emitter-testmetest@1.0.4
AI Security Review
scanned 2d ago · by lpm-firewall-aiSource inspection found an empty runtime entrypoint and no package lifecycle scripts. The build-time shell expression invokes that empty entrypoint, with no source evidence of a harmful effect.
Decision evidence
public snapshot- package.json names index.js as the package entrypoint and defines no lifecycle scripts.
- index.js exports an empty object and contains no runtime behavior.
- binding.gyp invokes index.js during build configuration, then returns a stub source name.
- binding.gyp uses a shell command during build configuration, but its invoked entrypoint is empty.
Source & flagged code
4 flagged · loading sourcebinding.gyp invokes index.js during build configuration, then returns a stub source name.
binding.gypView on unpkg · L1package.json names index.js as the package entrypoint and defines no lifecycle scripts.
package.jsonView on unpkg · L1Findings
Affected versions and remediation
This report applies to event-emitter-testmetest@1.0.4.
See all versions of event-emitter-testmetest for other recorded verdicts.
- Review the evidence and your use of event-emitter-testmetest@1.0.4 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.