test-flow-entire6
This report shows the evidence for test-flow-entire6@1.0.0. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-14320 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The package is an inert metadata export, but its URL-pinned external dependency creates an unresolved supply-chain payload path. This supports a warning rather than a block.
Independent scan evidence
public snapshot- package.json declares a direct dependency fetched from a non-registry staging host.
- npm-shrinkwrap.json locks bundle-token-region-resolve to that same external URL.
- package.json has no lifecycle scripts.
- index.js only exports static name and version metadata.
- No executable, harvesting, shell, persistence, or network code exists in the package files.
Source & flagged code
1 flagged · loading sourcepackage.json declares a direct dependency fetched from a non-registry staging host.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to test-flow-entire6@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing test-flow-entire6@1.0.0. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.