</>PackageGraphPackageGraph

rsc.io/binaryregexp

Go Modulesvv0.2.0

Go module: rsc.io/binaryregexp

Not recommended for new projects

No — rsc.io/binaryregexp should not be adopted for new projects. Depended on by 2 known packages. Last published 2665 days ago. 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.

  • FMaintenance: grade F, Failing.

    Last published 2665 days ago.

  • ?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 rsc.io/binaryregexp 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 rsc.io/binaryregexp.

Relationship graph

Dependencies (left) and dependents (right) of rsc.io/binaryregexp.

cloud.google.com/…github.com/google…rsc.io/binaryrege…
rsc.io/binaryregexp dependencies dependents

Frequently installed together

Release history

No releases in the last two years.

Recent versions of rsc.io/binaryregexp
VersionPublishedLicense
v0.2.0latest7 years ago
v0.1.07 years ago

Overview

rsc.io/binaryregexp is an Go Modules package that go module: rsc.io/binaryregexp. It has 2 known dependents in the graph. The latest version is v0.2.0.

Who should use it

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

No — rsc.io/binaryregexp should not be adopted for new projects. Depended on by 2 known packages. Last published 2665 days ago. No license declared — you have no explicit right to use this code.

How do I install rsc.io/binaryregexp?

Run `go get rsc.io/binaryregexp` to add rsc.io/binaryregexp to your Go Modules project.

What license is rsc.io/binaryregexp released under?

No license was detected in rsc.io/binaryregexp's metadata; review the repository before use.

How popular is rsc.io/binaryregexp?

Go Modules does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on rsc.io/binaryregexp.

Is rsc.io/binaryregexp still maintained?

The most recent release of rsc.io/binaryregexp (vv0.2.0) was published 7 years ago.