</>PackageGraphPackageGraph

sigs.k8s.io/yaml

Go Modulesvv1.6.0

Go module: sigs.k8s.io/yaml

Not recommended for new projects

No — sigs.k8s.io/yaml should not be adopted for new projects. Depended on by 8 known packages. Last published 412 days ago. 2 releases in the last 2 years. No license declared — you have no explicit right to use this code.

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

    Depended on by 8 known packages.

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

    Last published 412 days ago. 2 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Pulls in 4 transitive packages.

  • 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/yaml to a project.

4
Direct dependencies

Runtime packages this one declares itself.

4
Total installed

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

1
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Go
No constraint declared

Dependencies

Declared by sigs.k8s.io/yaml vv1.6.0. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on sigs.k8s.io/yaml.

Relationship graph

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

Frequently installed together

Release history

2 releases in the last two years, typically about 596 days apart.

Recent versions of sigs.k8s.io/yaml
VersionPublishedLicense
v1.6.0latest1 year ago
v1.5.01 year ago
v1.4.02 years ago
v1.3.05 years ago
v1.2.06 years ago
v1.1.07 years ago
v1.0.09 years ago

Overview

sigs.k8s.io/yaml is an Go Modules package that go module: sigs.k8s.io/yaml. It has 8 known dependents in the graph. The latest version is v1.6.0.

Who should use it

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

  • Actively published to the registry.

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/yaml?

No — sigs.k8s.io/yaml should not be adopted for new projects. Depended on by 8 known packages. Last published 412 days ago. 2 releases in the last 2 years. No license declared — you have no explicit right to use this code.

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

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

How many dependencies does sigs.k8s.io/yaml have?

sigs.k8s.io/yaml declares 4 direct dependencies and pulls in 4 packages in total once its runtime tree is resolved.

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

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

How popular is sigs.k8s.io/yaml?

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

Is sigs.k8s.io/yaml still maintained?

The most recent release of sigs.k8s.io/yaml (vv1.6.0) was published 1 year ago.