@feedmepos/mf-payment@1.11.10
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 hook’s relative target could extend installation effects beyond this package, but the available source does not establish its scope or intent. This warrants a warning, not a publish block.
Decision evidence
public snapshot- package.json defines an automatic postinstall that runs pnpm install in a relative sibling directory, whose scope is unclear.
- The inspected application entrypoint exports package modules; the flagged dynamic require appears in a guarded built-in-module fallback.
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.11.10.
See all versions of @feedmepos/mf-payment for other recorded verdicts.
- Review the evidence and your use of @feedmepos/mf-payment@1.11.10 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.