@skhema/embed@0.3.0
Embeddable component for integrating strategic elements with Skhema.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe scanner's exfiltration signal corresponds to disclosed, package-aligned browser analytics for the embed component, not credential theft or covert payload behavior. Source inspection found no install-time execution or malicious execution chain.
Decision evidence
public snapshot- Runtime posts embed content, page URL/title, and user agent to analytics.skhema.com.
- Analytics is enabled unless the rendered element sets track-analytics="false".
- A 24-hour _sk cookie deduplicates tracked content hashes.
- package.json has no preinstall, install, or postinstall hook.
- Network activity is confined to the named Skhema analytics endpoint and uses credentials:"omit".
- Tracking activates only when browser custom elements are connected and a contributor ID is present.
- No credential harvesting, filesystem access, shell execution, dynamic code execution, or remote payload loading 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.3.0.
See all versions of @skhema/embed for other recorded verdicts.
- Review the evidence and your use of @skhema/embed@0.3.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.