registry / eacq-payform-core / 0.0.0-stage
eacq-payform-core@0.0.0-stage
Temporary package placeholder for staged publishing
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected manifest identifies a stub and declares no install hooks or runtime entrypoints. No malicious behavior was identified in the package snapshot.
Static reason
No blocking static signals were detected.
Trigger
None identified; no lifecycle hook or runtime entrypoint is declared.
Impact
No malicious behavior was established from the inspected source.
Mechanism
The manifest contains package metadata and marks the package as a stub.
AI rationale
The inspected manifest identifies a stub and declares no install hooks or runtime entrypoints. No malicious behavior was identified in the package snapshot.
Evidence
package.json
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest marks this as a stub and contains no lifecycle scripts or runtime entrypoints.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "eacq-payform-core",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Lifecycle Evidence
The manifest marks this as a stub and contains no lifecycle scripts or runtime entrypoints.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to eacq-payform-core@0.0.0-stage.
See all versions of eacq-payform-core for other recorded verdicts.
- Review the evidence and your use of eacq-payform-core@0.0.0-stage 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.