go.opentelemetry.io/collector/component/componentstatus
Go Modulesvv0.160.0Go module: go.opentelemetry.io/collector/component/componentstatus
Not recommended for new projects
No — go.opentelemetry.io/collector/component/componentstatus should not be adopted for new projects. Depended on by 2 known packages. Pulls in 78 transitive packages (at least — some of the tree is still being crawled). No license declared — you have no explicit right to use this code.
- CAdoption: grade C, Fair — worth a look.
Depended on by 2 known packages.
- AMaintenance: grade A, Excellent.
Last published 8 days ago. 50 releases in the last 2 years.
- DWeight: grade D, Poor — a real concern.
Pulls in 78 transitive packages (at least — some of the tree is still being crawled).
- 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 go.opentelemetry.io/collector/component/componentstatus to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Longest resolved dependency chain below this package.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Compatibility
- Go
- No constraint declared
Dependencies
Declared by go.opentelemetry.io/collector/component/componentstatus vv0.160.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (17)
Used by
Popular packages that depend on go.opentelemetry.io/collector/component/componentstatus.
Go module: github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatocumulativeprocessor
Go module: go.opentelemetry.io/collector/processor/processortest
Relationship graph
Dependencies (left) and dependents (right) of go.opentelemetry.io/collector/component/componentstatus.
Frequently installed together
Go module: go.uber.org/zap
Go module: github.com/go-logr/logr
Go module: github.com/stretchr/testify
Go module: go.uber.org/multierr
Go module: github.com/hashicorp/go-version
Go module: golang.org/x/sys
Go module: github.com/google/uuid
Go module: github.com/modern-go/concurrent
Go module: github.com/json-iterator/go
Go module: github.com/cespare/xxhash/v2
Go module: github.com/modern-go/reflect2
Go module: github.com/go-logr/stdr
Release history
50 releases in the last two years, typically about 14 days apart.
| Version | Published | License |
|---|---|---|
| v0.160.0latest | 8 days ago | — |
| v0.159.0 | 23 days ago | — |
| v0.158.0 | 1 month ago | — |
| v0.157.0 | 1 month ago | — |
| v0.156.0 | 2 months ago | — |
| v0.155.0 | 2 months ago | — |
| v0.154.0 | 3 months ago | — |
| v0.153.0 | 3 months ago | — |
| v0.152.1 | 3 months ago | — |
| v0.152.0 | 4 months ago | — |
| v0.151.0 | 4 months ago | — |
| v0.150.0 | 4 months ago | — |
| v0.149.0 | 5 months ago | — |
| v0.148.0 | 5 months ago | — |
| v0.147.0 | 6 months ago | — |
Overview
go.opentelemetry.io/collector/component/componentstatus is an Go Modules package that go module: go.opentelemetry.io/collector/component/componentstatus. It has 2 known dependents in the graph. The latest version is v0.160.0.
Who should use it
Teams working in the Go Modules ecosystem who need go module: go.opentelemetry.io/collector/component/componentstatus and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your Go Modules stack.
Pros
- Actively published to the registry.
Cons
- Large dependency tree (17 direct dependencies) increases install size and audit surface.
- 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 go.opentelemetry.io/collector/component/componentstatus?
No — go.opentelemetry.io/collector/component/componentstatus should not be adopted for new projects. Depended on by 2 known packages. Pulls in 78 transitive packages (at least — some of the tree is still being crawled). No license declared — you have no explicit right to use this code.
How do I install go.opentelemetry.io/collector/component/componentstatus?
Run `go get go.opentelemetry.io/collector/component/componentstatus` to add go.opentelemetry.io/collector/component/componentstatus to your Go Modules project.
How many dependencies does go.opentelemetry.io/collector/component/componentstatus have?
go.opentelemetry.io/collector/component/componentstatus declares 17 direct dependencies and pulls in 78 packages in total once its runtime tree is resolved.
What license is go.opentelemetry.io/collector/component/componentstatus released under?
No license was detected in go.opentelemetry.io/collector/component/componentstatus's metadata; review the repository before use.
How popular is go.opentelemetry.io/collector/component/componentstatus?
Go Modules does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on go.opentelemetry.io/collector/component/componentstatus.
Is go.opentelemetry.io/collector/component/componentstatus still maintained?
The most recent release of go.opentelemetry.io/collector/component/componentstatus (vv0.160.0) was published 8 days ago.