Summary
Togoder Security scanned the Go package github.com/gofrs/uuid@v4.4.0+incompatible on Oct 5, 2026. An AI review of 5 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
CWE-330: Use of Insufficiently Random Values
NPS-85F9FBD223F6
V6 and V7 UUIDs use a clock sequence as a monotonic counter. The clock sequence is shared between V1, V6, and V7 and is not reset between generations. This is not a security vulnerability in this context but may be noted for predictability in some use cases. However, no malicious intent is present.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| codec.go | safe | Cleared by Jev triage; no further analysis needed |
| fuzz.go | safe | Cleared by Jev triage; no further analysis needed |
| generator.go | safe | No malicious patterns detected; the code is a legitimate UUID generation library with standard cryptographic practices. |
| sql.go | safe | Cleared by Jev triage; no further analysis needed |
| uuid.go | safe | Cleared by Jev triage; no further analysis needed |
Frequently asked questions
Is github.com/gofrs/uuid safe to use?
Our AI source review of github.com/gofrs/uuid@v4.4.0+incompatible found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does github.com/gofrs/uuid contain malware?
No malware was identified in github.com/gofrs/uuid@v4.4.0+incompatible when Togoder Security scanned it on Oct 5, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was github.com/gofrs/uuid checked?
Togoder Security downloaded the published Go package and had an AI model read its 5 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan github.com/gofrs/uuid together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in github.com/gofrs/uuid@v4.4.0+incompatible, cost nothing.