Vulnerability Database · npm · @semantic-release/github · Version

@semantic-release/github 12.0.10

No vulnerabilities in this database cover 12.0.10.

Every vulnerability Vulert holds for @semantic-release/github was tested against this version and none of them covers it. That is the good answer, not a guarantee — the package page shows which versions are affected.

Critical 0 High 0 Medium 0 Low 0 Unrated 0

All @semantic-release/github versions & vulnerabilities → Source repository Search the database for this package →

Released 21 Sep 2026 Status latest release Licence MIT Also known from other sources 0 Newer releases 192 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

Scan your app free →

01 Vulnerabilities affecting this version

@semantic-release/github 12.0.10 vulnerabilities

No vulnerability in the Vulert database covers @semantic-release/github 12.0.10. See the versions that are affected →

Looking for another version, or everything Vulert holds for @semantic-release/github?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram

Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.

Join the channel →

Questions

About @semantic-release/github 12.0.10

Is @semantic-release/github 12.0.10 vulnerable?

No. No vulnerability in the Vulert database covers @semantic-release/github 12.0.10. Every vulnerability Vulert holds for @semantic-release/github was tested against this release and none of them covers it — the good answer, though not a guarantee, since new vulnerabilities are published for packages all the time.

Is 12.0.10 the latest release of @semantic-release/github?

Yes. 12.0.10 is the current release, published 21 Sep 2026. Staying on the current line is what keeps you inside the publisher's fixes.

How do I monitor @semantic-release/github for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @semantic-release/github version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.