@feedmepos/mf-inventory-portal@1.8.2
## Description
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe active runtime forwards an existing session token to a fixed account host that differs from the API backend hosts. Because the source does not establish the recipient's authorization, this is an unresolved credential exposure risk rather than confirmed malicious exfiltration.
Decision evidence
public snapshot- The package exports dist/app.js, which imports the bundle containing the token refresh code.
- On an API 401, the request wrapper passes the current session token to refreshAuth; that routine posts it to a fixed account.feedmedev.cc endpoint.
- The ordinary API backend is built from feedmeapi.com hosts, distinct from the fixed token recipient. The source does not establish whether that recipient is an authorized account service.
- The token transfer is part of a 401 refresh flow and uses a fixed account endpoint; inspected source does not establish malicious use or that the recipient is unrelated.
Source & flagged code
7 flagged · loading sourcePackage source references dynamic code evaluation.
dist/EmailDialog.vue_vue_type_script_setup_true_lang-CAEf3irc.jsView on unpkg · L30140Findings
Affected versions and remediation
This report applies to @feedmepos/mf-inventory-portal@1.8.2.
See all versions of @feedmepos/mf-inventory-portal for other recorded verdicts.
- Review the evidence and your use of @feedmepos/mf-inventory-portal@1.8.2 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.