@feedmepos/mf-payment@1.10.7
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 automatic postinstall's relative sibling install target has unresolved effects, warranting a warning. Inspected runtime code supports ordinary document viewing and does not establish concrete malicious behavior or a block-eligible attack.
Decision evidence
public snapshot- `package.json` defines an automatic postinstall that runs `pnpm -C ../package install`; the sibling target and effects are unresolved.
- The published entrypoint is `dist/app.js`; the flagged dynamic `require` is inside a guarded fallback in the document viewer bundle.
- The document viewer gets a URL through the app API before fetching it; the inspected code does not establish an unrelated credential recipient.
- The inspected bundle behavior is consistent with document viewing and worker compatibility; it does not establish a malicious payload or data theft.
- The stylesheet imports Google Fonts, which is consistent with ordinary UI styling.
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.7.
See all versions of @feedmepos/mf-payment for other recorded verdicts.
- Review the evidence and your use of @feedmepos/mf-payment@1.10.7 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.