atomic-meta-check
SECURITY PLACEHOLDER — reserves the unclaimed unscoped bin name of @coveo/atomic-component-health-check to prevent a dependency-confusion (npxconfuse) hijack. This is NOT the real tool; use @coveo/atomic-component-health-check.
This report shows the evidence for atomic-meta-check@0.0.1, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package's stated placeholder purpose does not require automatic external telemetry. Its postinstall beacon exfiltrates host-derived data through both HTTPS and DNS.
Decision evidence
public snapshot- postinstall executes beacon.js automatically.
- Beacon sends hostname, platform, Node version, and CI status to an external OAST host.
- DNS fallback embeds hostname-derived label in lookup.
- CLI only displays a placeholder notice and exits.
- No file reads, shell execution, or payload loading found.
Source & flagged code
2 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpostinstall executes beacon.js automatically.
package.jsonView on unpkg · L8Findings
Affected versions and remediation
This report applies to atomic-meta-check@0.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing atomic-meta-check@0.0.1. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.