@feedmepos/mf-payment@1.10.3
Development always based on production and add "-beta.version" in behind. Every deployment from development to production will increment based on semantic versioninig.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall command creates an unresolved install-time side effect because its relative target varies by installation layout. The flagged dynamic loader and stylesheet excerpt do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines a postinstall hook that runs pnpm install from the relative path ../package, whose effect depends on the install environment.
- The flagged Function/require code is a caught dynamic module-loading fallback in a bundled file; no malicious payload behavior was established there.
- The package entrypoint is a frontend module and its stylesheet imports Google Fonts; these inspected excerpts do not indicate credential collection or exfiltration.
Source & flagged code
8 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 unpkgSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
Findings
Affected versions and remediation
This report applies to @feedmepos/mf-payment@1.10.3.
See all versions of @feedmepos/mf-payment for other recorded verdicts.
- Review the evidence and your use of @feedmepos/mf-payment@1.10.3 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.