@sarimarcus/content-sites-ui@0.43.0
Universal Astro UI components, layout shell and design tokens shared by the content sites.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no lifecycle hooks and exports source modules for an Astro UI package. The network references inspected serve affiliate widgets, consent analytics, and an explicitly configured browser tool API; no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest exports source modules; the required Astro and CSS files provide reusable site UI, page shells, navigation, and styles.
- Affiliate scripts use fixed provider endpoints and load through the widget or visitor-triggered loader paths.
- Analytics events enter the GTM data layer through a consent check, and the analytics component is limited to production builds.
- WebMCP setup is an exported browser API; remote tools require caller-supplied endpoint and definitions and send a request only when executed.
Source & flagged code
8 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
src/affiliate/AffiliateBandShell.astroView on unpkgThe manifest exports source modules; the required Astro and CSS files provide reusable site UI, page shells, navigation, and styles.
src/affiliate/AffiliateBandShell.astroView on unpkg · L18Findings
Affected versions and remediation
This report applies to @sarimarcus/content-sites-ui@0.43.0.
See all versions of @sarimarcus/content-sites-ui for other recorded verdicts.
- Review the evidence and your use of @sarimarcus/content-sites-ui@0.43.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.