@semantic-release/error 2.1.0

errors with more than just a message

@semantic-release/error@2.1.0 was published on 2017-10-29. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @semantic-release/error versions · Permanent reference to 2.1.0 · Latest release

Package specifications

Version2.1.0
License declarationMIT
Published2017-10-29T19:38:25.209Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars11
Repository forks6

Install @semantic-release/error 2.1.0

npm install @semantic-release/error@2.1.0
pnpm add @semantic-release/error@2.1.0
yarn add @semantic-release/error@2.1.0

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

    How to interpret the specifications

    Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

    Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

    OpenSSF repository checks

    Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

    Maintained10/10 — 25 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Binary-Artifacts10/10 — no binaries found in the repo
    Pinned-Dependencies10/10 — all dependencies are pinned
    Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    Security-Policy10/10 — security policy file detected
    Packaging10/10 — packaging workflow detected
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness