Vulnerability Database · Go · Package report

github.com/qpoint-io/rulekit: vulnerability history, versions and safety

github.com/qpoint-io/rulekit is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/qpoint-io/rulekit v0.0.0-20260515133857-5a9f2181df74 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260515133857-5a9f2181df74, the version you would install today, has no known vulnerabilities.

Package health score 70/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.0-20260515133857-5a9f2181df74 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 13 i
  • Last release 5 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/qpoint-io/rulekit, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20260515133857-5a9f2181df74 15 May 2026 none MIT — Details →
v0.0.0-20260309182111-4008a61da80f 09 Mar 2026 none MIT — Details →
v0.0.0-20260218135034-5986cb29b7f8 18 Feb 2026 none MIT — Details →
v0.0.0-20251216173107-36bea2f2ea48 16 Dec 2025 none MIT — Details →
v0.0.0-20251014161302-8e15a5fafcb5 14 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20250911144811-30bb2f88c146 11 Sep 2025 none Apache-2.0 — Details →
v0.0.0-20250609174947-482155cf0825 09 Jun 2025 none Apache-2.0 — Details →
v0.0.0-20250523153529-ebcc650d83d2 23 May 2025 none Apache-2.0 — Details →
v0.0.0-20250520133345-50b8c2fe01a9 20 May 2025 none Apache-2.0 — Details →
v0.0.0-20250519122419-41639eff799c 19 May 2025 none Apache-2.0 — Details →
v0.0.0-20250514145718-044b7a5d363e 14 May 2025 none Apache-2.0 — Details →
v0.0.0-20250514143429-8bfcf8d9ea84 14 May 2025 none Apache-2.0 — Details →
v0.0.0-20250514114029-0108c80c0af9 14 May 2025 none Apache-2.0 — Details →
v0.0.0-20250513182400-6be0c746b9af 13 May 2025 none Apache-2.0 — Details →
v0.0.0-20250513133001-032cf0af00da 13 May 2025 none Apache-2.0 — Details →
v0.0.0-20250508200956-174860d1b724 08 May 2025 none Apache-2.0 — Details →
v0.0.0-20250507174636-ee845ba87977 07 May 2025 none Apache-2.0 — Details →
v0.0.0-20250506180944-e7c3b91a39d0 06 May 2025 none Apache-2.0 — Details →
v0.0.0-20250416182126-910bb49d6621 16 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250324153535-6b110fcefe0e 24 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20250319155219-ec495f164919 19 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20250314131233-557fb140ea90 14 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20250313211439-c880c0b83711 13 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20250312183244-677a8c86c02c 12 Mar 2025 none Apache-2.0 — Details →

All 24 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.

03 Vulnerabilities

Recorded vulnerabilities for github.com/qpoint-io/rulekit

No vulnerability write-ups match this view

Search all 0 in the database →

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 github.com/qpoint-io/rulekit

Is github.com/qpoint-io/rulekit safe to use?

Vulert has no vulnerabilities on record for github.com/qpoint-io/rulekit in Go 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 github.com/qpoint-io/rulekit's Vulert package health score?

Vulert scores github.com/qpoint-io/rulekit 70/100, which reads as in good shape. 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).

Is the latest version of github.com/qpoint-io/rulekit affected?

No. v0.0.0-20260515133857-5a9f2181df74, 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 github.com/qpoint-io/rulekit should I use?

v0.0.0-20260515133857-5a9f2181df74 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 github.com/qpoint-io/rulekit have?

0 vulnerabilities are recorded for github.com/qpoint-io/rulekit in the Go 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 github.com/qpoint-io/rulekit vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/qpoint-io/rulekit 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 github.com/qpoint-io/rulekit 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 github.com/qpoint-io/rulekit for upcoming vulnerabilities?

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