dccxx-s3-explorer@1.0.153-hoaphat
A production ready, batteries included starter template for Vite + React projects
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection supports a warning for hardcoded credentials and broad cloud-management capability, but not a publish block for malware. Suspicious scanner hits are mostly bundled MSAL/axios/React app behavior or user-invoked product functionality.
Decision evidence
public snapshot- dist/s3-explorer.js contains a hardcoded Bearer JWT in an Authorization header for get-knowledge-base API calls.
- dist/s3-explorer.js embeds Google API key/client ID and Azure MSAL client/redirect config.
- Runtime UI stores OAuth/access tokens in localStorage for SharePoint, OneDrive, and Google Drive integrations.
- package.json has no install/postinstall hook; prepare is husky and prepublishOnly only runs build when publishing.
- Entrypoints export React components/API_BASE_URL and do not run network calls on package import alone.
- Network, localStorage, metadata, and file delete/upload actions are aligned with an S3/cloud file explorer UI and user actions.
- Scanner cloud metadata hit is bundled @azure/msal-common constant, not package-specific credential harvesting.
Source & flagged code
8 flagged · loading sourcePackage contains a critical-looking secret pattern.
dist/s3-explorer.umd.cjsView on unpkg · L1096Source 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.153-hoaphat.
See all versions of dccxx-s3-explorer for other recorded verdicts.
- Review the evidence and your use of dccxx-s3-explorer@1.0.153-hoaphat 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.