</>PackageGraphPackageGraph

modernc.org/libc

Go Modulesvv1.75.6

Go module: modernc.org/libc

Not recommended for new projects

No — modernc.org/libc should not be adopted for new projects. Depended on by 4 known packages. No license declared — you have no explicit right to use this code.

  • CAdoption: grade C, Fair — worth a look.

    Depended on by 4 known packages.

  • ?Maintenance: grade ?, Not reported by this registry.

    No publish date reported for the latest release.

  • ?Weight: grade ?, Not reported by this registry.

    No dependency or size data collected for this package yet.

  • BSupply chain: grade B, Good.

    This package lists no maintainer.

  • FLicense: grade F, Failing.

    No license declared — you have no explicit right to use this code.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding modernc.org/libc to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Go
No constraint declared

Used by

Popular packages that depend on modernc.org/libc.

Relationship graph

Dependencies (left) and dependents (right) of modernc.org/libc.

Frequently installed together

Release history

25 releases in the last two years, typically about 17 days apart.

Recent versions of modernc.org/libc
VersionPublishedLicense
v1.75.420 days ago
v1.75.31 month ago
v1.75.21 month ago
v1.75.11 month ago
v1.75.01 month ago
v1.74.21 month ago
v1.74.02 months ago
v1.73.52 months ago
v1.73.03 months ago
v1.68.16 months ago
v1.67.77 months ago
v1.67.67 months ago
v1.67.48 months ago
v1.67.28 months ago
v1.67.09 months ago

Overview

modernc.org/libc is an Go Modules package that go module: modernc.org/libc. It has 4 known dependents in the graph. The latest version is v1.75.6.

Who should use it

Teams working in the Go Modules ecosystem who need go module: modernc.org/libc and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your Go Modules stack.

Pros

  • Zero runtime dependencies — minimal footprint.

Cons

  • No license detected — review usage terms before adopting.

Auto-generated from collected registry metadata. No external claims are inferred.

Frequently asked questions

Should I use modernc.org/libc?

No — modernc.org/libc should not be adopted for new projects. Depended on by 4 known packages. No license declared — you have no explicit right to use this code.

How do I install modernc.org/libc?

Run `go get modernc.org/libc` to add modernc.org/libc to your Go Modules project.

What license is modernc.org/libc released under?

No license was detected in modernc.org/libc's metadata; review the repository before use.

How popular is modernc.org/libc?

Go Modules does not publish download counts. Within PackageGraph's crawl, 4 known packages depend on modernc.org/libc.

Is modernc.org/libc still maintained?

No publish date is reported for modernc.org/libc; check the repository for recent activity.