
Research
/Security News
Weaponizing Discord for Command and Control Across npm, PyPI, and RubyGems.org
Socket researchers uncover how threat actors weaponize Discord across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
jsm-sysinfo
Advanced tools
Comprehensive system monitoring implementation using the systeminformation npm package with TypeScript.
comprehensive system monitoring implementation using the systeminformation
npm package with TypeScript.
This will provide structured JSON output with both raw values and human-readable formats.I've created a comprehensive system monitoring implementation using the systeminformation
npm package with TypeScript.
Here's what the implementation provides:
npm install jsm-sysinfo
Structured JSON Output: Every piece of data includes:
name
: Programmatic identifierlabel
: Human-readable labelvalue
: Raw valuehumanValue
: Formatted, human-readable valueunit
: Optional unit of measurementComprehensive Monitoring Sections:
Utility Methods:
getSystemMonitoringData()
: Get all system data at oncegetSection(sectionName)
: Get specific section datastartMonitoring()
: Continuous monitoring with callbackData Formatting:
npm install jsm-sysinfo
import { SystemMonitor } from "jsm-sysinfo";
// One-time monitoring
const monitor = new SystemMonitor();
const data = await monitor.getSystemMonitoringData();
console.log(JSON.stringify(data, null, 2));
// Continuous monitoring
const intervalId = monitor.startMonitoring(5000, (data) => {
// Process monitoring data every 5 seconds
console.log(data);
});
// Get specific section
const cpuData = await monitor.getSection("cpu");
Example usage demonstrating various features of the SystemMonitor @example
import SystemMonitor, { IMonitorConfig } from "jsm-sysinfo";
async function demonstrateSystemMonitoring() {
// Create monitor with custom configuration
const config: IMonitorConfig = {
includeTemperature: true,
includeProcesses: true,
maxProcesses: 10,
includeNetworkStats: true,
includeBattery: true,
timeoutMs: 15000,
};
const monitor = new SystemMonitor(config);
try {
// Get quick overview
console.log("=== System Summary ===");
const summary = await monitor.getQuickSummary();
Object.entries(summary).forEach(([key, value]) => {
console.log(`${key}: ${value}`);
});
console.log("\n=== Full System Data ===");
// Get complete system data
const fullData = await monitor.collectAll();
console.log(JSON.stringify(fullData, null, 2));
// Get specific sections
console.log("\n=== CPU Section Only ===");
const cpuData = await monitor.getSection("cpu");
if (cpuData) {
cpuData.fields.forEach((field) => {
console.log(`${field.label}: ${field.humanValue}`);
});
}
// Start continuous monitoring
console.log("\n=== Starting Continuous Monitoring ===");
const stopMonitoring = monitor.startContinuousMonitoring(
10000,
(data, error) => {
if (error) {
console.error("Monitoring error:", error.message);
return;
}
if (data) {
const cpuSection = data.sections.find((s) => s.section === "CPU");
const memSection = data.sections.find((s) => s.section === "Memory");
const cpuLoad =
cpuSection?.fields.find((f) => f.name === "currentLoad")
?.humanValue || "N/A";
const memUsage =
memSection?.fields.find((f) => f.name === "usagePercent")
?.humanValue || "N/A";
console.log(
`[${new Date().toLocaleTimeString()}] CPU: ${cpuLoad}, Memory: ${memUsage}`
);
}
}
);
// Stop monitoring after 30 seconds
setTimeout(() => {
stopMonitoring();
console.log("Continuous monitoring stopped");
}, 30000);
} catch (error: any) {
console.error("System monitoring error:", error);
}
}
// Run the demonstration
// demonstrateSystemMonitoring();
@example
// Simple usage for basic monitoring
import SystemMonitor from "jsm-sysinfo";
async function basicMonitoring() {
const monitor = new SystemMonitor();
// Get all data once
const data = await monitor.collectAll();
// Extract key metrics
const cpuSection = data.sections.find((s) => s.section === "CPU");
const memSection = data.sections.find((s) => s.section === "Memory");
const cpuBrand = cpuSection?.fields.find(
(f) => f.name === "brand"
)?.humanValue;
const cpuLoad = cpuSection?.fields.find(
(f) => f.name === "currentLoad"
)?.humanValue;
const memTotal = memSection?.fields.find(
(f) => f.name === "total"
)?.humanValue;
const memUsage = memSection?.fields.find(
(f) => f.name === "usagePercent"
)?.humanValue;
console.log(`System: ${data.hostname}`);
console.log(`CPU: ${cpuBrand} - Load: ${cpuLoad}`);
console.log(`Memory: ${memUsage} of ${memTotal} used`);
console.log(`Uptime: ${formatDuration(data.uptime)}`);
console.log(`Data collected in ${data.summary.collectionTimeMs}ms`);
}
@example
// Advanced usage with custom configuration and filtering
import SystemMonitor, {
IMonitoringSection,
IMonitoringField,
} from "jsm-sysinfo";
async function advancedMonitoring() {
const monitor = new SystemMonitor({
includeTemperature: true,
includeProcesses: true,
maxProcesses: 3,
includeNetworkStats: false,
includeBattery: false,
});
const data = await monitor.collectAll();
// Filter and display only performance-related metrics
data.sections.forEach((section) => {
console.log(`\n=== ${section.section} ===`);
const performanceFields = section.fields.filter(
(field) =>
field.metadata?.category === "performance" ||
field.metadata?.realtime === true
);
performanceFields.forEach((field) => {
console.log(` ${field.label}: ${field.humanValue}`);
if (field.metadata?.sensitive) {
console.log(` [SENSITIVE DATA]`);
}
});
});
// Find all temperature readings
const tempFields: IMonitoringField[] = [];
data.sections.forEach((section) => {
section.fields.forEach((field) => {
if (field.metadata?.category === "thermal") {
tempFields.push(field);
}
});
});
if (tempFields.length > 0) {
console.log("\n=== Temperature Readings ===");
tempFields.forEach((field) => {
console.log(` ${field.label}: ${field.humanValue}`);
});
}
}
The implementation follows TypeScript best practices with proper type definitions, error handling, and modular design. Each monitoring field provides both raw data for programmatic use and formatted values for display purposes.
FAQs
Comprehensive system monitoring implementation using the systeminformation npm package with TypeScript.
We found that jsm-sysinfo demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
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.
Research
/Security News
Socket researchers uncover how threat actors weaponize Discord across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
Security News
Socket now integrates with Bun 1.3’s Security Scanner API to block risky packages at install time and enforce your organization’s policies in local dev and CI.
Research
The Socket Threat Research Team is tracking weekly intrusions into the npm registry that follow a repeatable adversarial playbook used by North Korean state-sponsored actors.