</>PackageGraphPackageGraph

github.com/moby/term

Go Modulesvv0.5.2

Go module: github.com/moby/term

Not recommended for new projects

No — github.com/moby/term should not be adopted for new projects. Depended on by 3 known packages. Last published 566 days ago. 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.

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

    Last published 566 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 3 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 github.com/moby/term to a project.

3
Direct dependencies

Runtime packages this one declares itself.

3
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 github.com/moby/term vv0.5.2. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on github.com/moby/term.

Relationship graph

Dependencies (left) and dependents (right) of github.com/moby/term.

Frequently installed together

Release history

1 release in the last two years, typically about 611 days apart.

Recent versions of github.com/moby/term
VersionPublishedLicense
v0.5.2latest1 year ago
v0.5.03 years ago
v0.5.13 years ago

Overview

github.com/moby/term is an Go Modules package that go module: github.com/moby/term. It has 3 known dependents in the graph. The latest version is v0.5.2.

Who should use it

Teams working in the Go Modules ecosystem who need go module: github.com/moby/term 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

  • Lean dependency tree (3 direct dependencies).

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 github.com/moby/term?

No — github.com/moby/term should not be adopted for new projects. Depended on by 3 known packages. Last published 566 days ago. No license declared — you have no explicit right to use this code.

How do I install github.com/moby/term?

Run `go get github.com/moby/term` to add github.com/moby/term to your Go Modules project.

How many dependencies does github.com/moby/term have?

github.com/moby/term declares 3 direct dependencies and pulls in 3 packages in total once its runtime tree is resolved.

What license is github.com/moby/term released under?

No license was detected in github.com/moby/term's metadata; review the repository before use.

How popular is github.com/moby/term?

Go Modules does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on github.com/moby/term.

Is github.com/moby/term still maintained?

The most recent release of github.com/moby/term (vv0.5.2) was published 1 year ago.