@skhema/embed
Embeddable component for integrating strategic elements with Skhema.
This report shows the evidence for @skhema/embed@0.2.0. 1 of 6 known versions is blocked or flagged. The newest version, 0.5.1, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is concrete default-on data exfiltration of rich application content to a hardcoded third-party endpoint, not merely ordinary local component behavior. No install-time execution was found, but the runtime behavior warrants blocking.
Decision evidence
public snapshot- dist/index.cjs posts embedded content, page URL/title, and user agent to analytics.skhema.com.
- Analytics activates on custom-element load; no explicit consent is required.
- Tracking is enabled by default; only track-analytics="false" disables it.
- Unload handlers use sendBeacon to preserve telemetry delivery.
- package.json has no npm lifecycle hooks.
- The behavior is browser runtime-only and uses credentials:"omit".
- No shell execution, dynamic code loading, or filesystem harvesting found.
Source & flagged code
1 flagged · loading sourceSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/embed.min.jsView on unpkgFindings
Affected versions and remediation
This report applies to @skhema/embed@0.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @skhema/embed@0.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.