Vulnerability Database · Go · Package report

github.com/hyperledger/aries-framework-go/component/kmscrypto: vulnerability history, versions and safety

github.com/hyperledger/aries-framework-go/component/kmscrypto 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/hyperledger/aries-framework-go/component/kmscrypto v0.0.0-20240327163625-64dd8acc0750 i

Updated on 23 Oct 2026

Good news: v0.0.0-20240327163625-64dd8acc0750, the version you would install today, has no known vulnerabilities.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

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

  • Current release v0.0.0-20240327163625-64dd8acc0750 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 238 i
  • OpenSSF scorecard 3/10 i
  • Last release 30 months ago i
  • Licence Apache-2.0 i

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

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/hyperledger/aries-framework-go/component/kmscrypto, 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-20240327163625-64dd8acc0750 27 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20230901120639-e17eddd3ad3e 01 Sep 2023 none Apache-2.0 — Details →
v0.0.0-20230831175038-717faacde1c0 31 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230828151543-984699876d28 28 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230828142456-5f00b6be8572 28 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230823143713-917ccf5c8cd2 23 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230822161205-69119012ed5c 22 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230822124109-5b0006954f6c 22 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230822115734-25cbbcb14f19 22 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230815195733-cce322df1e8f 15 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230810150537-71e132ba5968 10 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230804190826-50313f0971cf 04 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230802164416-cfa2433b1819 02 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230727134633-020b60b288ed 27 Jul 2023 none Apache-2.0 — Details →
v0.0.0-20230718141804-b2fdf798c242 18 Jul 2023 none Apache-2.0 — Details →
v0.0.0-20230717135750-1687924e30bf 17 Jul 2023 none Apache-2.0 — Details →
v0.0.0-20230704180706-7159d2ef444a 04 Jul 2023 none Apache-2.0 — Details →
v0.0.0-20230623182631-4c062f2515f9 23 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230622211121-852ce35730b4 22 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230622171716-43af8054a539 22 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230622082138-3ffab1691857 22 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230615141038-5d444d6c36de 15 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230615070726-b02a3e01fc44 15 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230612153955-e841db576f38 12 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230607135144-c0362fa570cc 07 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230605134811-1970e7e22384 05 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230531115220-0445e9664e8e 31 May 2023 none Apache-2.0 — Details →
v0.0.0-20230523162334-2e91159e2b9e 23 May 2023 none Apache-2.0 — Details →
v0.0.0-20230523152718-aa3f65b7ac13 23 May 2023 none Apache-2.0 — Details →
v0.0.0-20230523135653-2f2e9595514f 23 May 2023 none Apache-2.0 — Details →
v0.0.0-20230518140949-c98960d1d097 18 May 2023 none Apache-2.0 — Details →
v0.0.0-20230517133327-301aa0597250 17 May 2023 none Apache-2.0 — Details →
v0.0.0-20230517105250-ead111355603 17 May 2023 none Apache-2.0 — Details →
v0.0.0-20230516135652-20c4d4beb991 16 May 2023 none Apache-2.0 — Details →
v0.0.0-20230510161104-02840741a53a 10 May 2023 none Apache-2.0 — Details →
v0.0.0-20230510133410-a652ea87c845 10 May 2023 none Apache-2.0 — Details →
v0.0.0-20230509105644-bc155de31280 09 May 2023 none Apache-2.0 — Details →
v0.0.0-20230508170346-4b06af1fda02 08 May 2023 none Apache-2.0 — Details →
v0.0.0-20230502132040-97864d50314d 02 May 2023 none Apache-2.0 — Details →
v0.0.0-20230501135648-a9a7ad029347 01 May 2023 none Apache-2.0 — Details →
v0.0.0-20230428130345-88e3cdc0d1d7 28 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230427134832-0c9969493bd3 27 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230425184546-a8b546e29100 25 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230424164053-dbfff0c0e511 24 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230422220249-5e86119d91d1 22 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230420181140-7798567c6ed1 20 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230420151605-a45b1b02336f 20 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230419135525-69e0be06cda8 19 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230417184158-344a7f82c4c2 17 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230410143310-6013a6bfa55b 10 Apr 2023 none Apache-2.0 — Details →

All 50 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/hyperledger/aries-framework-go/component/kmscrypto

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/hyperledger/aries-framework-go/component/kmscrypto

Is github.com/hyperledger/aries-framework-go/component/kmscrypto safe to use?

Vulert has no vulnerabilities on record for github.com/hyperledger/aries-framework-go/component/kmscrypto 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/hyperledger/aries-framework-go/component/kmscrypto's Vulert package health score?

Vulert scores github.com/hyperledger/aries-framework-go/component/kmscrypto 60/100, which reads as usable, but worth attention. 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/hyperledger/aries-framework-go/component/kmscrypto affected?

No. v0.0.0-20240327163625-64dd8acc0750, 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/hyperledger/aries-framework-go/component/kmscrypto should I use?

v0.0.0-20240327163625-64dd8acc0750 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/hyperledger/aries-framework-go/component/kmscrypto have?

0 vulnerabilities are recorded for github.com/hyperledger/aries-framework-go/component/kmscrypto 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/hyperledger/aries-framework-go/component/kmscrypto vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/hyperledger/aries-framework-go/component/kmscrypto 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/hyperledger/aries-framework-go/component/kmscrypto 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/hyperledger/aries-framework-go/component/kmscrypto for upcoming vulnerabilities?

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