@mapvx/web-components-ssr@1.12.0
A modern, framework-agnostic web component built with Angular 22 that provides an interactive map and location discovery interface.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe scanner's Trojan Source flag is explained by a parser stripping a leading BOM, and I found no concrete credential theft or unrelated attack behavior. However, the entry point activates a fixed Google Analytics ID without a visible disclosure or opt-out, so the undisclosed runtime telemetry warrants a warning.
Decision evidence
public snapshot- The browser bundle embeds the fixed Google Analytics tracking ID `G-9KB6BB1J7M`.
- The entry point initializes Google Analytics with that ID when bootstrapping the `mapvx-website` custom element; automatic page views are disabled.
- The analytics module loads its tag from `www.googletagmanager.com` and runs its configured commands.
- The bundle also includes a Mapvx Sentry endpoint for error reporting.
- The flagged invisible character is a BOM check in an HTML/XML parser, not a bidi control used to disguise code.
- The manifest's `prepare` script runs `husky`; it declares no `preinstall`, `install`, or `postinstall` hook.
- The package is a browser component, and the examined network use is analytics, error reporting, and Mapvx service access consistent with that purpose.
- The source reviewed showed no credential collection, unrelated account actions, or install-time data transfer.
Source & flagged code
3 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/browser/chunk-D6zG2upO.jsView on unpkg · L2A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/browser/main.jsView on unpkgFindings
Affected versions and remediation
This report applies to @mapvx/web-components-ssr@1.12.0.
See all versions of @mapvx/web-components-ssr for other recorded verdicts.
- Review the evidence and your use of @mapvx/web-components-ssr@1.12.0 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.