test-flow-1
This report shows the evidence for test-flow-1@1.0.2. 2 of 3 known versions are 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-14319 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 itself is inert, but its direct external dependency is uninspected and lacks lockfile integrity evidence. This is an unresolved staged-payload supply-chain risk, not confirmed malicious code.
Independent scan evidence
public snapshot- package.json declares schema-format-memo-index from a direct external artifact URL.
- npm-shrinkwrap.json resolves that dependency without an integrity hash.
- Package and shrinkwrap/source versions disagree (1.0.2 vs 1.0.0).
- package.json has no lifecycle scripts.
- index.js only exports static name and version metadata.
- No source reads files, environment, credentials, or invokes network/shell code.
Source & flagged code
1 flagged · loading sourcepackage.json declares schema-format-memo-index from a direct external artifact URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to test-flow-1@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing test-flow-1@1.0.2. 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.