registry / @skhema/embed / 0.4.0
@skhema/embed@0.4.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 documented, fixed-endpoint embed analytics triggered by user-authored components. It is privacy-relevant telemetry but not a concrete malicious chain under the package-aligned/user-invoked boundary.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A browser renders a skhema-element or skhema-component with a contributor ID and analytics not disabled.
Impact
Transmits supplied embed content and page metadata to Skhema; no credential or local-file access is present.
Mechanism
Batched browser analytics POST/beacon telemetry.
AI rationale
The scanner's exfiltration signal corresponds to documented, fixed-endpoint embed analytics triggered by user-authored components. It is privacy-relevant telemetry but not a concrete malicious chain under the package-aligned/user-invoked boundary.
Evidence
package.jsondist/index.cjsdist/embed.min.jsREADME.md
Network endpoints1
analytics.skhema.com/functions/v1/embed-manage
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Browser runtime posts embed content, page URL/title, and user agent to Skhema analytics.
- Tracking is enabled unless track-analytics="false".
Evidence against
- package.json has no lifecycle hooks or bin entry.
- Telemetry is tied to rendered Skhema custom elements and supplied content.
- No credential/env/file harvesting, shell execution, eval, remote code loading, or AI-agent writes found.
- Requests omit credentials and use a fixed same-vendor endpoint.
Behavioral surface
Network
HighEntropyStringsMinifiedTelemetryUrlStrings
Source & flagged code
1 flagged · loading sourcedist/embed.min.jsView file
•Browser cookie sent to a fixed external endpoint in dist/embed.min.js:
!function(e,t){"object"==typeof exports&&"undefined"!=typeof module?t(exports):"function"==typeof define&&define.amd?define(["exports"],t):t((e="undefined"!=typeof globalThis?globa...
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/embed.min.jsView on unpkgFindings
1 Critical2 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/embed.min.js
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @skhema/embed@0.4.0.
See all versions of @skhema/embed for other recorded verdicts.
- Review the evidence and your use of @skhema/embed@0.4.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.