@semantic-release/commit-analyzer 13.0.1

semantic-release plugin to analyze commits with conventional-changelog

@semantic-release/commit-analyzer@13.0.1 was published on 2025-01-03. Its manifest declares 8 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=20.8.1.

All @semantic-release/commit-analyzer versions · Permanent reference to 13.0.1 · Latest release

Package specifications

Version13.0.1
License declarationMIT
Published2025-01-03T04:09:19.945Z
Node.js requirement>=20.8.1
Type declarationsNot declared
Runtime dependency count8
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size34.08 KiB
Published file count10
Package typemodule
ES module entryNot declared
Default entry./index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies28
Repository stars446
Repository forks82

Install @semantic-release/commit-analyzer 13.0.1

npm install @semantic-release/commit-analyzer@13.0.1
pnpm add @semantic-release/commit-analyzer@13.0.1
yarn add @semantic-release/commit-analyzer@13.0.1

Runtime dependencies

Peer requirements

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review0/10 — Found 0/1 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Maintained10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Pinned-Dependencies10/10 — all dependencies are pinned
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