Vulnerability Database · npm · Package report

sign-addon: vulnerability history, versions and safety

Q: How do I monitor sign-addon for upcoming vulnerabilities?

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

sign-addon is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sign-addon vulnerabilities

Vulert verdict on sign-addon 6.4.0 i

Updated on 23 Oct 2026

Good news: 6.4.0, the version you would install today, has no known vulnerabilities.

Package health score 44/100

Security Minor issues
Maintenance Deprecated
Popularity Niche
Community Inactive

The registry marks the latest release as deprecated, which caps this score.

What to do: Stay on 6.4.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.4.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

Current release 6.4.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 2 packages i
Stars 69 i
OpenSSF scorecard 1/10 i
Last release 33 months ago i
Licence MPL-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for sign-addon, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
6.4.0	09 Jan 2024	none	MPL-2.0	—	Details →
6.3.0	28 Sep 2023	none	MPL-2.0	—	Details →
6.2.0	11 Sep 2023	none	MPL-2.0	—	Details →
6.1.0	17 Jul 2023	none	MPL-2.0	—	Details →
6.0.0	20 Mar 2023	none	MPL-2.0	—	Details →
5.3.0	07 Mar 2023	none	MPL-2.0	—	Details →
5.2.0	02 Jan 2023	none	MPL-2.0	—	Details →
5.1.0	04 Oct 2022	none	MPL-2.0	—	Details →
5.0.0	07 Jun 2022	none	MPL-2.0	—	Details →
4.1.0	31 May 2022	none	MPL-2.0	—	Details →
4.0.1	25 Mar 2022	none	MPL-2.0	—	Details →
4.0.0	25 Mar 2022	none	MPL-2.0	—	Details →
3.11.0	07 Feb 2022	none	MPL-2.0	—	Details →
3.10.0	18 Jan 2022	none	MPL-2.0	—	Details →
3.9.0	22 Sep 2021	none	MPL-2.0	—	Details →
3.8.0	06 Sep 2021	none	MPL-2.0	—	Details →
3.7.0	10 Aug 2021	none	MPL-2.0	—	Details →
3.6.0	02 Aug 2021	none	MPL-2.0	—	Details →
3.5.0	10 May 2021	none	MPL-2.0	—	Details →
3.4.0	26 Apr 2021	none	MPL-2.0	—	Details →
3.3.0	09 Feb 2021	none	MPL-2.0	—	Details →
3.2.0	19 Jan 2021	none	MPL-2.0	—	Details →
3.1.0	15 Sep 2020	none	MPL-2.0	—	Details →
3.0.0	29 Jul 2020	none	MPL-2.0	—	Details →
2.0.6	23 Jun 2020	none	MPL-2.0	—	Details →
2.0.5	20 Jan 2020	none	MPL-2.0	—	Details →
2.0.4	19 Dec 2019	none	MPL-2.0	—	Details →
2.0.3	16 Dec 2019	none	MPL-2.0	—	Details →
2.0.2	09 Dec 2019	none	MPL-2.0	—	Details →
2.0.1	29 Nov 2019	none	MPL-2.0	—	Details →
2.0.0	25 Nov 2019	none	MPL-2.0	—	Details →
1.0.0	31 Oct 2019	none	MPL-2.0	—	Details →
0.3.1	23 May 2018	none	MPL-2.0	—	Details →
0.3.0	14 Feb 2018	none	MPL-2.0	—	Details →
0.2.2	01 Nov 2017	none	MPL-2.0	—	Details →
0.2.1	30 Jan 2017	none	MPL-2.0	—	Details →
0.2.0	06 Oct 2016	none	MPL-2.0	—	Details →
0.1.4	15 Sep 2016	none	MPL-2.0	—	Details →
0.1.3	20 Jul 2016	none	MPL-2.0	—	Details →
0.1.2	14 Jul 2016	none	MPL-2.0	—	Details →
0.1.1	11 Jul 2016	none	MPL-2.0	—	Details →
0.1.0	07 Jul 2016	none	MPL-2.0	—	Details →
0.0.4	24 Jun 2016	none	MPL-2.0	—	Details →
0.0.3	12 May 2016	none	MPL-2.0	—	Details →
0.0.1	28 Mar 2016	none	MPL-2.0	—	Details →

All 45 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for sign-addon

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 sign-addon

Is sign-addon safe to use?

Vulert has no vulnerabilities on record for sign-addon in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is sign-addon's Vulert package health score?

Vulert scores sign-addon 44/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of sign-addon affected?

No. 6.4.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of sign-addon should I use?

6.4.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does sign-addon have?

0 vulnerabilities are recorded for sign-addon in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sign-addon vulnerabilities disclosed?

0 vulnerabilities were recorded for sign-addon in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sign-addon are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor sign-addon for upcoming vulnerabilities?

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