@getmicdrop/venue-calendar@4.3.141
A customizable Svelte calendar component for displaying comedy events
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package performs default runtime tracking to its first-party service, including visitor and page attribution data, while its documented consent control does not stop the event requests. This is a telemetry privacy risk rather than evidence of credential theft or unrelated malicious behavior.
Decision evidence
public snapshot- Calendar startup emits widget_load and link_click tracking events unless arrival tracking was already recorded.
- The runtime posts event records to MicDrop’s default API, including session, visitor and device IDs, plus referrer and page URL when its consent check permits those fields.
- The consent check controls those attribution fields, while the tracking POST itself still runs.
- The README says consent-required holds tracking until consent is granted, which does not match the unconditional tracking request.
- The beacons go to the package’s first-party service and track calendar interactions, which may support its venue analytics features.
- The README documents consent options and configurable API settings.
Source & flagged code
9 flaggedA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/venue-calendar.umd.jsView on unpkgFindings
Affected versions and remediation
This report applies to @getmicdrop/venue-calendar@4.3.141.
See all versions of @getmicdrop/venue-calendar for other recorded verdicts.
- Review the evidence and your use of @getmicdrop/venue-calendar@4.3.141 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.