registry / @columenlabs/lumen-ui / 0.1.166
@columenlabs/lumen-ui@0.1.166
Lumen: shared React components (frame, views, widgets, charts, drawers).
AI Security Review
scanned 6d ago · by lpm-firewall-aiThis version is a React component library with no install lifecycle scripts or executable bin. The flagged telemetry and browser storage behaviors are explicitly invoked by consumers and fit the package’s purpose.
Static reason
No blocking static signals were detected.
Trigger
An application must mount useLumenTelemetry to start telemetry; query persistence runs only when a caller supplies the persist option.
Impact
No credential theft, unrelated data collection, install-time behavior, or harmful automatic action was found in the reviewed paths.
Mechanism
Telemetry posts app/version and limited event metadata to the configured endpoint, defaulting to /api/t. Query persistence stores successful query state in browser localStorage.
AI rationale
This version is a React component library with no install lifecycle scripts or executable bin. The flagged telemetry and browser storage behaviors are explicitly invoked by consumers and fit the package’s purpose.
Network endpoints1
/api/t
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package is a shared React component library whose main entry points to dist/index.js.
- Telemetry is exposed as a hook and starts when an app mounts it; it posts batches to the configured endpoint, defaulting to /api/t.
- Telemetry reports app and version with route, event, device and request metadata; error reports use an error class and stack hash.
- Query data persistence is opt-in through the persist option and uses browser localStorage, with a size limit and sign-out clearing.
Evidence against
- The manifest contains no install lifecycle scripts or executable bin.
- The main entry is a barrel of library exports; the reviewed telemetry hook is not invoked there.
- The package’s browser storage behavior is query caching and UI state, not access to host files or credentials.
Behavioral surface
FilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
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.166",
"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": "./dist/index.d.ts",
"default": "./dist/index.js"
},
"./ui/*": {
"types": "./dist/ui/*.d.ts",
"default": "./dist/ui/*.js"
},
"./people": {
"types": "./dist/people/index.d.ts",
"default": "./dist/people/index.js"
},
"./assistant": {
"types": "./
Low
Ai Review Evidence
The package is a shared React component library whose main entry points to dist/index.js.
Findings
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.js
LowAi Review Evidencedist/telemetry.js
LowAi Review Evidencedist/query-client.js
Affected versions and remediation
This report applies to @columenlabs/lumen-ui@0.1.166.
See all versions of @columenlabs/lumen-ui for other recorded verdicts.
- Review the evidence and your use of @columenlabs/lumen-ui@0.1.166 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.