Vulnerability Database · Go · Package report
github.com/hectane/go-acl: vulnerability history, versions and safety
github.com/hectane/go-acl 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.
Vulert verdict on github.com/hectane/go-acl 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 Sustainable
- 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 129 i
- OpenSSF scorecard 2/10 i
- Last release 4 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/hectane/go-acl, 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.
- v1.0.0 11 Jun 2026
- v0.0.0-20260611235401-760bcb4ad881 11 Jun 2026
- v0.0.0-20230225031251-cdfc9e3acf94 25 Feb 2023
- v0.0.0-20230122075934-ca0b05cb1adb 22 Jan 2023
- v0.0.0-20210915132429-884d594b08b3 15 Sep 2021
- v0.0.0-20190604041725-da78bae5fc95 04 Jun 2019
- v0.0.0-20190603165650-eada576e864d 03 Jun 2019
- v0.0.0-20190602021054-68e29f77cb5b 02 Jun 2019
- v0.0.0-20190529191421-0d0c96583e86 29 May 2019
- v0.0.0-20190529191405-a432b8a8604f 29 May 2019
- v0.0.0-20190523051433-dfeb47f3e2ef 23 May 2019
- v0.0.0-20190523044847-878cc285d69c 23 May 2019
- v0.0.0-20190523043933-0a8ab9f24f8b 23 May 2019
- v0.0.0-20190227043046-e28f47eff0c4 27 Feb 2019
- v0.0.0-20190225143042-ca730a35e3a8 25 Feb 2019
- v0.0.0-20190112205748-6937c4c474eb 12 Jan 2019
- v0.0.0-20151103031024-7f56832555fc 03 Nov 2015
- v0.0.0-20151102224826-043db197847c 02 Nov 2015
- v0.0.0-20151101033129-32b4b9baa846 01 Nov 2015
- v0.0.0-20151031210829-4ca538b933a8 31 Oct 2015
- v0.0.0-20151030232758-fce792ad53ad 30 Oct 2015
All 21 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/hectane/go-acl
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/hectane/go-acl
Is github.com/hectane/go-acl safe to use?
Vulert has no vulnerabilities on record for github.com/hectane/go-acl 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/hectane/go-acl's Vulert package health score?
Vulert scores github.com/hectane/go-acl 68/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/hectane/go-acl 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/hectane/go-acl 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/hectane/go-acl have?
0 vulnerabilities are recorded for github.com/hectane/go-acl 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/hectane/go-acl vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/hectane/go-acl 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/hectane/go-acl 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/hectane/go-acl for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hectane/go-acl version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.