Vulnerability Database · Go · Package report

github.com/cyberphone/json-canonicalization: vulnerability history, versions and safety

github.com/cyberphone/json-canonicalization 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/cyberphone/json-canonicalization v0.0.0-20261011152517-32a48195b9b2 i

Updated on 23 Oct 2026

Good news: v0.0.0-20261011152517-32a48195b9b2, the version you would install today, has no known vulnerabilities.

Package health score 70/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release v0.0.0-20261011152517-32a48195b9b2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 154 i
  • OpenSSF scorecard 1/10 i
  • Last release this month 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/cyberphone/json-canonicalization, 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-20261011152517-32a48195b9b2 11 Oct 2026 none Apache-2.0 — Details →
v0.0.0-20261011151737-0c88af095879 11 Oct 2026 none Apache-2.0 — Details →
v0.0.0-20241213102144-19d51d7fe467 13 Dec 2024 none Apache-2.0 — Details →
v0.0.0-20231217050601-ba74d44ecf5f 17 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231217050223-1b5643774554 17 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231210205546-134a08932483 10 Dec 2023 none Apache-2.0 — Details →
v0.0.0-20231126122549-61ad448c9768 26 Nov 2023 none Apache-2.0 — Details →
v0.0.0-20231011164504-785e29786b46 11 Oct 2023 none Apache-2.0 — Details →
v0.0.0-20230710064741-aa7fe85c7dbd 10 Jul 2023 none Apache-2.0 — Details →
v0.0.0-20230708081258-2b684ae0d7c4 08 Jul 2023 none Apache-2.0 — Details →
v0.0.0-20230701045847-91eb5f1b7744 01 Jul 2023 none Apache-2.0 — Details →
v0.0.0-20230514072755-504adb8a8af1 14 May 2023 none Apache-2.0 — Details →
v0.0.0-20230514070733-359e917ddc62 14 May 2023 none Apache-2.0 — Details →
v0.0.0-20220623050100-57a0ce2678a7 23 Jun 2022 none Apache-2.0 — Details →
v0.0.0-20220622203553-1b5190c23d2a 22 Jun 2022 none Apache-2.0 — Details →
v0.0.0-20220216171627-b6721b06b4ef 16 Feb 2022 none Apache-2.0 — Details →
v0.0.0-20220216160050-919c1ede6842 16 Feb 2022 none Apache-2.0 — Details →
v0.0.0-20210823021906-dc406ceaf94b 23 Aug 2021 none Apache-2.0 — Details →
v0.0.0-20210823021551-a54520de8726 23 Aug 2021 none Apache-2.0 — Details →
v0.0.0-20210813032746-922b04a0e1cb 13 Aug 2021 none Apache-2.0 — Details →
v0.0.0-20210810063702-dce61d6e0ff9 10 Aug 2021 none Apache-2.0 — Details →
v0.0.0-20210809183623-32f37087b35d 09 Aug 2021 none Apache-2.0 — Details →
v0.0.0-20210303052042-6bc126869bf4 03 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210204075859-f9218ae53759 04 Feb 2021 none Apache-2.0 — Details →
v0.0.0-20200921175456-169095496608 21 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200703052342-77e15c5d8e47 03 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200703051012-4e46f6e90a85 03 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200417180520-cd6247b5f11e 17 Apr 2020 none Apache-2.0 — Details →
v0.0.0-20200120161146-ed051aa347c5 20 Jan 2020 none Apache-2.0 — Details →
v0.0.0-20190911193413-11869ed2704c 11 Sep 2019 none Apache-2.0 — Details →
v0.0.0-20190906052032-99485dd5642d 06 Sep 2019 none Apache-2.0 — Details →
v0.0.0-20190904133355-f143284db843 04 Sep 2019 none Apache-2.0 — Details →
v0.0.0-20190315070602-0d3bc5fdbe49 15 Mar 2019 none Apache-2.0 — Details →
v0.0.0-20190208074244-65ec3ec4957a 08 Feb 2019 none Apache-2.0 — Details →
v0.0.0-20190207092147-27bed033039c 07 Feb 2019 none Apache-2.0 — Details →
v0.0.0-20190205165832-7604ba94dc03 05 Feb 2019 none Apache-2.0 — Details →
v0.0.0-20190202070801-1dec68808f97 02 Feb 2019 none Apache-2.0 — Details →
v0.0.0-20190201053051-34b43c90daa9 01 Feb 2019 none Apache-2.0 — Details →
v0.0.0-20190130042116-369854470f15 30 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190128164027-8fbfd8ffcfa0 28 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190127160609-61d133890d3b 27 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190124085007-058cff82e5d8 24 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190124065037-27b6731b3b57 24 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190123165824-2e4b79945f5a 23 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190119154149-7044b642a988 19 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190118072017-77eb1402ad89 18 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190117192954-a8dc80d6cd9b 17 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190116174115-70f622aeb01e 16 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190115153836-9ac7ffb46814 15 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190113141847-a0484e38d1ed 13 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190112145638-2728c6dd0e48 12 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190111071421-2198d7a6b1ae 11 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190110090958-047e220b05d2 10 Jan 2019 none Apache-2.0 — Details →

All 53 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/cyberphone/json-canonicalization

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/cyberphone/json-canonicalization

Is github.com/cyberphone/json-canonicalization safe to use?

Vulert has no vulnerabilities on record for github.com/cyberphone/json-canonicalization 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/cyberphone/json-canonicalization's Vulert package health score?

Vulert scores github.com/cyberphone/json-canonicalization 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/cyberphone/json-canonicalization affected?

No. v0.0.0-20261011152517-32a48195b9b2, 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/cyberphone/json-canonicalization should I use?

v0.0.0-20261011152517-32a48195b9b2 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/cyberphone/json-canonicalization have?

0 vulnerabilities are recorded for github.com/cyberphone/json-canonicalization 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/cyberphone/json-canonicalization vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/cyberphone/json-canonicalization 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/cyberphone/json-canonicalization 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/cyberphone/json-canonicalization for upcoming vulnerabilities?

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