registry / @columenlabs/lumen-ui / 0.1.140
@columenlabs/lumen-ui@0.1.140
Lumen: shared React components (frame, views, widgets, charts, drawers).
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged network and storage APIs support app API calls, error reporting, optional telemetry, and browser cache persistence. The inspected code showed no install-time activity, unrelated collector, or concealed behavior.
Static reason
No blocking static signals were detected.
Trigger
App code mounts the telemetry hook, calls an API adapter, or enables query-cache persistence.
Impact
No malicious impact identified; network activity is directed to app routes and cache data remains in browser storage.
Mechanism
Telemetry posts to a configurable endpoint that defaults to `/api/t`; assistant and people clients use caller-provided app API bases. Query-cache persistence uses browser localStorage.
AI rationale
The flagged network and storage APIs support app API calls, error reporting, optional telemetry, and browser cache persistence. The inspected code showed no install-time activity, unrelated collector, or concealed behavior.
Network endpoints4
/api/t/api/client-error/api/assistant (documented default base)/api/people (documented default base)
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies this as a shared React component package and exposes built UI modules as its entry points.
- Telemetry starts when an app mounts `useLumenTelemetry`; its endpoint is configurable and defaults to the same-origin `/api/t`.
- Telemetry points use route templates and limited fields such as error class, stack hash, request ID, status, and web-vitals measurements.
- The assistant client sends requests to a caller-supplied base URL, documented with `/api/assistant` as the app route.
- Query-cache persistence is browser `localStorage` storage, with an explicit persistence option.
Evidence against
- The manifest contains no install, preinstall, or postinstall scripts.
- The inspected fetch clients target app routes and provide no hard-coded external collector.
- No credential harvesting, unsolicited account actions, concealed execution, or filesystem persistence was identified.
Behavioral surface
FilesystemNetworkWebSocket
Source & flagged code
6 flaggeddist/assistant/lumen-assistant.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 5
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/assistant/lumen-assistant.js#virtual:normalized:round1View on unpkgpackage.jsonView file
1{
"name": "@columenlabs/lumen-ui",
"version": "0.1.140",
"description": "Lumen: shared React components (frame, views, widgets, charts, drawers).",
"license": "MIT",
"type": "module",
"main": "./dist/index.js",
"types": "./dist/index.d.ts",
"exports": {
".": {
"types": "./d
Low
Ai Review Evidence
The manifest identifies this as a shared React component package and exposes built UI modules as its entry points.
package.jsonView on unpkg · L1Findings
1 High1 Medium8 Low
HighSemantic Analysis Limiteddist/assistant/lumen-assistant.js#virtual:normalized:round1
MediumNetwork
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowAi Review Evidencepackage.json
LowAi Review Evidencedist/telemetry.js
LowAi Review Evidencedist/telemetry.d.ts
LowAi Review Evidencedist/assistant/client.js
LowAi Review Evidencedist/query-client.js
Affected versions and remediation
This report applies to @columenlabs/lumen-ui@0.1.140.
See all versions of @columenlabs/lumen-ui for other recorded verdicts.
- Review the evidence and your use of @columenlabs/lumen-ui@0.1.140 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.