
Research
Malicious Go “crypto” Module Steals Passwords and Deploys Rekoobe Backdoor
An impersonated golang.org/x/crypto clone exfiltrates passwords, executes a remote shell stager, and delivers a Rekoobe backdoor on Linux.
@flakiness/sdk
Advanced tools
Comprehensive SDK for creating and managing Flakiness JSON Reports in Node.js
The Flakiness SDK provides a comprehensive set of tools for creating and managing Flakiness JSON Reports in Node.js.
npm i @flakiness/sdk
Here's a minimal example of creating a Flakiness JSON Report:
import {
FlakinessReport,
GitWorktree,
ReportUtils,
writeReport,
uploadReport,
CIUtils
} from '@flakiness/sdk';
// Initialize git worktree and environment
const worktree = GitWorktree.create(process.cwd());
const env = ReportUtils.createEnvironment({ name: 'CI' });
// Create a simple test report
const report: FlakinessReport.Report = {
category: 'testreport',
commitId: worktree.headCommitId(),
url: CIUtils.runUrl(),
environments: [env],
suites: [{
title: 'My Test Suite',
type: 'describe',
tests: [{
title: 'My Test',
location: { file: 'test.spec.ts', line: 10, column: 1 },
attempts: [{
environmentIdx: 0,
status: 'passed',
expectedStatus: 'passed',
duration: 100 as FlakinessReport.DurationMS,
}],
}],
}],
startTimestamp: Date.now() as FlakinessReport.UnixTimestampMS,
duration: 100 as FlakinessReport.DurationMS,
};
// Write report to disk or upload to Flakiness.io
await writeReport(report, [], './flakiness-report');
// Or: await uploadReport(report, [], { flakinessAccessToken: 'your-token' });
The SDK provides two entry points:
@flakiness/sdkThe main entry point for Node.js environments. Provides full access to all SDK functionality including:
@flakiness/sdk/browserA browser-compatible entry point with a subset of utilities that work in browser environments. Exports:
FlakinessReport - Type definitions for the report formatReportUtils - Browser-safe utilities (normalizeReport, stripAnsi, visitTests)Use this entry point when you need to process or manipulate reports in browser-based tools or web applications.
FlakinessReport - Type definitions and validation for the Flakiness JSON Report formatCIUtils - Utilities to extract CI/CD information (run URLs, environment detection)GitWorktree - Git repository utilities for path conversion and commit informationReportUtils - Namespace with utilities for report creation and manipulation:
createEnvironment() - Create environment objects with system informationnormalizeReport() - Deduplicate environments, suites, and testscollectSources() - Extract source code snippets for locations in the reportstripAnsi() - Remove ANSI escape codes from stringsvisitTests() - Recursively visit all tests in a reportcreateFileAttachment() / createDataAttachment() - Create report attachmentsCPUUtilization - Track CPU utilization over time via periodic samplingRAMUtilization - Track RAM utilization over time via periodic samplingshowReport() - Start a local server and open the report in your browseruploadReport() - Upload reports and attachments to Flakiness.iowriteReport() - Write reports to disk in the standard Flakiness report formatFlakinessProjectConfig - Manage project configuration stored in .flakiness/config.jsonFAQs
Comprehensive SDK for creating and managing Flakiness JSON Reports in Node.js
We found that @flakiness/sdk 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
An impersonated golang.org/x/crypto clone exfiltrates passwords, executes a remote shell stager, and delivers a Rekoobe backdoor on Linux.

Security News
npm rolls out a package release cooldown and scalable trusted publishing updates as ecosystem adoption of install safeguards grows.

Security News
AI agents are writing more code than ever, and that's creating new supply chain risks. Feross joins the Risky Business Podcast to break down what that means for open source security.