@feedmepos/mf-payment
Development always based on production and add "-beta.version" in behind. Every deployment from development to production will increment based on semantic versioninig.
This report shows the evidence for @feedmepos/mf-payment@1.11.6. 1 of 9 known versions is blocked or flagged. The newest version, 1.11.10, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a concrete automatic install hook that runs a package manager against an external relative directory. The browser bundle findings do not mitigate this install-time mutation.
Decision evidence
public snapshot- Its automatic postinstall runs pnpm install in the external relative directory ../package.
- That command can mutate another project and run that project's dependency lifecycle hooks without user action.
- No credential harvesting, exfiltration endpoint, or runtime self-dependency was found.
- The flagged DocumentViewer dynamic code is bundled compatibility code; its bidi characters are isolate markers.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage contains a high-severity secret pattern.
dist/app-rcbXu2mv.jsView on unpkg · L19173Findings
Affected versions and remediation
This report applies to @feedmepos/mf-payment@1.11.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing @feedmepos/mf-payment@1.11.6. 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.