</>PackageGraphPackageGraph

sigs.k8s.io/json

Go Modulesvv0.0.0-20260909141634-11ed52e25bc5

Go module: sigs.k8s.io/json

Not recommended for new projects

No — sigs.k8s.io/json should not be adopted for new projects. Depended on by 3 known packages. No license declared — you have no explicit right to use this code.

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

    Depended on by 3 known packages.

  • AMaintenance: grade A, Excellent.

    Last published today. 2 releases in the last 2 years.

  • ?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 sigs.k8s.io/json 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 sigs.k8s.io/json.

Relationship graph

Dependencies (left) and dependents (right) of sigs.k8s.io/json.

Frequently installed together

Release history

2 releases in the last two years.

Recent versions of sigs.k8s.io/json
VersionPublishedLicense
v0.0.0-20260909141634-11ed52e25bc5latest16 hours ago
v0.0.0-20250730193827-2d320260d730latest1 year ago

Overview

sigs.k8s.io/json is an Go Modules package that go module: sigs.k8s.io/json. It has 3 known dependents in the graph. The latest version is v0.0.0-20260909141634-11ed52e25bc5.

Who should use it

Teams working in the Go Modules ecosystem who need go module: sigs.k8s.io/json 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 sigs.k8s.io/json?

No — sigs.k8s.io/json should not be adopted for new projects. Depended on by 3 known packages. No license declared — you have no explicit right to use this code.

How do I install sigs.k8s.io/json?

Run `go get sigs.k8s.io/json` to add sigs.k8s.io/json to your Go Modules project.

What license is sigs.k8s.io/json released under?

No license was detected in sigs.k8s.io/json's metadata; review the repository before use.

How popular is sigs.k8s.io/json?

Go Modules does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on sigs.k8s.io/json.

Is sigs.k8s.io/json still maintained?

The most recent release of sigs.k8s.io/json (vv0.0.0-20260909141634-11ed52e25bc5) was published 16 hours ago.