dccxx-s3-explorer@1.0.128
⚠ Under reviewA production ready, batteries included starter template for Vite + React projects
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe critical metadata match is consistent with bundled MSAL's optional Azure region discovery, and the inspected lifecycle hooks do not show an install-time attack. I cannot mark the package clean because the source for its declared @azure/msal-browser dependency remained unresolved in the supplied dependency evidence.
Decision evidence
public snapshot- The manifest declares @azure/msal-browser; its selected dependency source remained unresolved in the supplied dependency evidence.
- The flagged metadata request is part of bundled MSAL region discovery and is used when no region value is configured.
- The package's prepare hook runs Husky, while prepublishOnly runs the build.
- The bundle configures Microsoft consumer sign-in with a package-associated redirect URI; inspection did not establish credential forwarding to an unrelated recipient.
- The inspected source did not establish a credential theft or install-time attack.
Source & flagged code
6 flagged · loading sourceSource appears to collect browser login credentials for exfiltration.
dist/s3-explorer.umd.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to dccxx-s3-explorer@1.0.128.
See all versions of dccxx-s3-explorer for other recorded verdicts.
- Review the evidence and your use of dccxx-s3-explorer@1.0.128 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.