New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

sensorcore

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

sensorcore

SensorCore SDK for JavaScript & TypeScript — logging, analytics, and remote config for browser and Node.js

npmnpm
Version
1.0.0
Version published
Weekly downloads
8
-11.11%
Maintainers
1
Weekly downloads
 
Created
Source

SensorCore JavaScript SDK

TypeScript SDK for sending logs to your SensorCore server. Zero external dependencies, works in browser and Node.js 18+.

Installation

npm install sensorcore

Quick Start

import SensorCore from 'sensorcore';

// 1. Configure once at app startup
SensorCore.configure({
  apiKey: 'sc_your_api_key',
  host: 'https://api.sensorcore.dev',
});

// 2a. Fire-and-forget — no await needed, never throws (most common)
SensorCore.log('App launched');
SensorCore.log('User signed up', { level: 'info', userId: 'user-uuid-123' });
SensorCore.log('Payment failed', { level: 'error', metadata: { code: 'card_declined', amount: 99 } });

// 2b. Async/await — when you need delivery confirmation
try {
  await SensorCore.logAsync('Critical error', { level: 'error' });
} catch (err) {
  console.error('Log failed:', err);
}

Configuration Options

ParameterTypeDefaultDescription
apiKeystringYour project API key
hoststringYour SensorCore server URL
defaultUserIdstring?undefinedAuto-attached user ID for every log
enabledbooleantrueSet false to silence all logs (e.g. in tests)
timeoutnumber10000Network request timeout in milliseconds
persistFailedLogsbooleantrueSave failed logs for auto-retry
maxPendingLogsnumber500Max entries buffered offline
pendingLogMaxAgenumber86400Drop buffered entries older than this (seconds)

Full config example

SensorCore.configure({
  apiKey: 'sc_abc123',
  host: 'https://api.sensorcore.dev',
  defaultUserId: currentUser?.id,
  enabled: process.env.NODE_ENV !== 'test',
  timeout: 15_000,
  persistFailedLogs: true,
  maxPendingLogs: 500,
  pendingLogMaxAge: 86400,
});

Log Levels

LevelUse case
'info'General events (default)
'warning'Recoverable issues
'error'Failures — triggers error indicator in dashboard
'messages'User-facing messages / chat events

Metadata

Pass a flat object with string, number, or boolean values. Unsupported types (arrays, nested objects, null) are silently dropped.

SensorCore.log('Purchase completed', {
  metadata: {
    product_id: 'sku-42',
    price: 9.99,
    is_trial: false,
    attempt: 1,
  },
});

Error Handling

When using logAsync, you can catch typed SensorCoreError:

import { SensorCoreError } from 'sensorcore';

try {
  await SensorCore.logAsync('Event');
} catch (err) {
  if (err instanceof SensorCoreError) {
    switch (err.code) {
      case 'not_configured':  break; // forgot to call configure()
      case 'network_error':   break; // no internet / timeout
      case 'server_error':    break; // server returned 4xx / 5xx
      case 'encoding_failed': break; // metadata serialisation failed
      case 'rate_limited':    break; // server returned 429
    }
  }
}

Rate Limiting

If the server returns HTTP 429, the SDK activates a circuit breaker with exponential backoff (60s → 120s → 300s → 600s max). After the cooldown expires, logging is automatically resumed. A successful request resets the backoff timer.

Offline Buffering

When a log fails to send (e.g. no internet), the SDK automatically:

  • Saves the entry to storage (localStorage in browser, ~/.sensorcore/pending.json in Node.js)
  • Monitors connectivity (online event in browser)
  • Retries all pending entries when the network returns
  • Flushes entries from previous sessions on next startup

Each entry keeps its original timestamp from when log() was called.

Safeguards:

  • Max 500 entries stored — oldest dropped when full
  • Max 3 retry attempts per entry — then permanently dropped
  • 24-hour TTL — stale entries are pruned automatically
  • Configurable via persistFailedLogs, maxPendingLogs, pendingLogMaxAge
  • Set persistFailedLogs: false to disable entirely

Remote Config

Fetch feature flags from your SensorCore server at runtime — no app release needed.

const config = await SensorCore.remoteConfig();

// Typed accessors — always undefined-safe, never crash
if (config.bool('show_new_onboarding') === true) {
  showNewOnboarding();
}
const timeout = config.number('api_timeout_seconds') ?? 30;
const variant = config.string('paywall_variant') ?? 'control';
const retries = config.int('max_retries') ?? 3;

remoteConfig() never throws — if the server is unreachable it returns an empty config.

AccessorReturnsNotes
bool(key)boolean | undefinedundefined if absent or wrong type
string(key)string | undefinedundefined if absent or wrong type
number(key)number | undefinedAny numeric value
int(key)number | undefinedOnly exact integers
get(key)unknownRaw value
config.rawRecord<string, unknown>Full decoded dictionary

Requirements

  • Browser: Any modern browser with fetch support
  • Node.js: 18+ (native fetch)
  • TypeScript: 5.0+ (optional — works with plain JavaScript too)

License

MIT

Keywords

logging

FAQs

Package last updated on 28 Feb 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts