registry / @graphysdk/react / 1.9.0-beta.1792583687354
@graphysdk/react@1.9.0-beta.1792583687354
⚠ Under reviewGraphy charting SDK for React
AI Security Review
scanned 14d ago · by lpm-firewall-aiInspected telemetry is limited to a chart summary sent to a vendor endpoint in production browser use and can be disabled. The required renderer dependency is unresolved in the available source snapshot, so the package cannot be cleared or classified as malicious from this inspection.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Using the package runtime invokes the imported renderer; rendering a provider with a scene in a production browser can also trigger chart telemetry.
Impact
No harmful effect is established by inspected source; the unavailable renderer leaves runtime behavior uncertain.
Mechanism
The package sends a one-time chart summary to its fixed Graphy Sentry endpoint, with an explicit provider opt-out. The unresolved renderer source prevents a complete assessment of that runtime path.
AI rationale
Inspected telemetry is limited to a chart summary sent to a vendor endpoint in production browser use and can be disabled. The required renderer dependency is unresolved in the available source snapshot, so the package cannot be cleared or classified as malicious from this inspection.
Evidence
package.jsondist/index.mjsdist/editable.browser.mjs
Network endpoints1
o4505108638597120.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares the renderer dependency, and the runtime entrypoint imports its provider and kit; the renderer source was unavailable for review, leaving this runtime path unresolved.
- The provider sends a one-time chart summary to the fixed Graphy Sentry endpoint only in a production browser, and `telemetry={false}` disables the send.
- The inspected telemetry payload contains chart-shape metadata, such as chart counts and types, rather than chart rows or labels.
Evidence against
- The inspected telemetry path is vendor-directed, limited to production browser use, and guarded by the provider opt-out.
- The available visualization-engine install hook only prints an install message. No concrete attack behavior was established in the inspected source.
Behavioral surface
EnvironmentVarsEvalFilesystem
HighEntropyStringsMinifiedTelemetryUrlStrings
Source & flagged code
4 flaggeddist/editable.browser.mjsView file
•stage = ast_semantic_analysis; reason = ast_path_work_budget_exceeded; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/editable.browser.mjsView on unpkgdist/index.cjsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @graphysdk/react@1.9.0-beta.1792580582727
matchedIdentity = npm:QGdyYXBoeXNkay9yZWFjdA:1.9.0-beta.1792580582727
similarity = 0.750
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.cjsView on unpkgpackage.json
Findings
2 High1 Medium9 Low
HighSemantic Analysis Limiteddist/editable.browser.mjs
HighPrevious Version Dangerous Deltadist/index.cjs
MediumEnvironment Vars
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowNo License
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Dependency Evidencedist/index.mjs
Affected versions and remediation
This report applies to @graphysdk/react@1.9.0-beta.1792583687354.
See all versions of @graphysdk/react for other recorded verdicts.
- Review the evidence and your use of @graphysdk/react@1.9.0-beta.1792583687354 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.