spectra-assure

Detect tampering and malware in software packages via behavioral differential analysis.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill spectra-assure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-assure
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/spectra-assure/skills/spectra-assure
Command: npx skills add https://github.com/dreadnode/capabilities --skill spectra-assure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard supply chain scanning tools fail to detect tampering and malicious insertions in compiled artifacts that signature-based SCA tools miss, leaving teams vulnerable to compromised dependencies that pass traditional vulnerability checks.

Core Features & Use Cases

  • Tampering Detection: Diff behavioral changes between two versions of the same package to catch hidden malicious insertions that signature-based tools miss.
  • Comprehensive Scanning: Scan individual packages by PURL, manifest files (requirements.txt, package.json, etc.), and lockfiles for malware, vulnerabilities, and policy violations.
  • Compliance Support: Map findings to NIST SSDF, EO 14028, and OWASP Top 10 requirements for audit and attestation workflows.
  • Use Case: When a dependency releases an unexpected minor/patch update, use the skill to diff the old and new versions to identify new network endpoints, shell execution indicators, or filesystem writes that signal tampering.

Quick Start

Use the spectra-assure skill to scan your project's requirements.txt file for supply chain risks using the hardened profile and review any flagged packages for malware or tampering indicators.

Frequently Asked Questions about spectra-assure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect package tampering and malware in my project dependencies?

You can detect package tampering and malware by scanning manifest files like requirements.txt or package.json using behavioral differential analysis. This process diffs behavioral changes between package versions to catch hidden malicious insertions that signature-based scanning tools routinely miss.

How does behavioral differential analysis find malicious insertions in third-party packages?

Behavioral differential analysis finds malicious insertions by comparing the runtime behavior of two versions of the same package. It identifies new network endpoints, shell execution indicators, and filesystem writes that signal a dependency has been compromised or tampered with.

Can I scan lockfiles and manifests for supply chain security risks?

Yes, you can scan lockfiles and manifest files for supply chain security risks, malware, and policy violations. The tool evaluates individual packages by PURL and parses dependency manifests to identify vulnerabilities and tampering indicators.

Do I need ReversingLabs API credentials to scan packages for vulnerabilities?

Yes, you need valid ReversingLabs API credentials to execute scans and interpret risk findings. You must provide an RL_TOKEN, and Enterprise users also need to configure RL_PORTAL_SERVER and RL_PORTAL_ORG environment variables to generate reports.

How do I triage a suspicious minor dependency upgrade for compromise?

To triage a suspicious minor dependency upgrade, diff the old and new versions using behavioral analysis to identify new network endpoints or shell execution indicators. This helps determine if the unexpected update introduces tampering or malicious behavior.

Can package scanning help with NIST SSDF and OWASP A06:2021 compliance attestation?

Yes, package scanning helps with compliance attestation by mapping security findings to NIST SSDF, EO 14028, and OWASP A06:2021 requirements. It generates reports that document vulnerability scans and supply chain risk assessments for audit workflows.