Vulnerability Database · Go · Package report
github.com/muhammadmuzzammil1998/jsonc: vulnerability history, versions and safety
github.com/muhammadmuzzammil1998/jsonc is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
See all github.com/muhammadmuzzammil1998/jsonc vulnerabilities
Vulert verdict on github.com/muhammadmuzzammil1998/jsonc v1.0.0 i
Updated on 23 Oct 2026
Good news: v1.0.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Quiet
What to do: Stay on v1.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 203 i
- OpenSSF scorecard 2/10 i
- Last release 54 months ago i
- Licence MIT 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/muhammadmuzzammil1998/jsonc, 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.
- v0.0.0-20220325123524-22f138d0c1e0 25 Mar 2022
- v1.0.0 25 Mar 2022
- v0.0.0-20220325121500-452c7dbab32c 25 Mar 2022
- v0.0.0-20220325105748-a626a9b9943f 25 Mar 2022
- v0.0.0-20211230184646-baf1f7156737 30 Dec 2021
- v0.0.0-20211230182209-a1565b71444b 30 Dec 2021
- v0.0.0-20201229145248-615b0916ca38 29 Dec 2020
- v0.0.0-20200627155943-e1c384b63054 27 Jun 2020
- v0.0.0-20200303171503-1e787b591db7 03 Mar 2020
- v0.0.0-20190906142622-1265e9b150c6 06 Sep 2019
- v0.0.0-20190902132743-e4903c4dea48 02 Sep 2019
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20220325123524-22f138d0c1e0 | 25 Mar 2022 | none | MIT | — | Details → |
| v1.0.0 | 25 Mar 2022 | none | MIT | — | Details → |
| v0.0.0-20220325121500-452c7dbab32c | 25 Mar 2022 | none | MIT | — | Details → |
| v0.0.0-20220325105748-a626a9b9943f | 25 Mar 2022 | none | MIT | — | Details → |
| v0.0.0-20211230184646-baf1f7156737 | 30 Dec 2021 | none | MIT | — | Details → |
| v0.0.0-20211230182209-a1565b71444b | 30 Dec 2021 | none | MIT | — | Details → |
| v0.0.0-20201229145248-615b0916ca38 | 29 Dec 2020 | none | MIT | — | Details → |
| v0.0.0-20200627155943-e1c384b63054 | 27 Jun 2020 | none | MIT | — | Details → |
| v0.0.0-20200303171503-1e787b591db7 | 03 Mar 2020 | none | MIT | — | Details → |
| v0.0.0-20190906142622-1265e9b150c6 | 06 Sep 2019 | none | MIT | — | Details → |
| v0.0.0-20190902132743-e4903c4dea48 | 02 Sep 2019 | none | MIT | — | Details → |
All 11 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/muhammadmuzzammil1998/jsonc
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
Questions
About github.com/muhammadmuzzammil1998/jsonc
Is github.com/muhammadmuzzammil1998/jsonc safe to use?
Vulert has no vulnerabilities on record for github.com/muhammadmuzzammil1998/jsonc 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/muhammadmuzzammil1998/jsonc's Vulert package health score?
Vulert scores github.com/muhammadmuzzammil1998/jsonc 50/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/muhammadmuzzammil1998/jsonc affected?
No. v1.0.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 github.com/muhammadmuzzammil1998/jsonc should I use?
v1.0.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 github.com/muhammadmuzzammil1998/jsonc have?
0 vulnerabilities are recorded for github.com/muhammadmuzzammil1998/jsonc 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/muhammadmuzzammil1998/jsonc vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/muhammadmuzzammil1998/jsonc 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/muhammadmuzzammil1998/jsonc 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/muhammadmuzzammil1998/jsonc for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/muhammadmuzzammil1998/jsonc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.