@lezer/go

Release historydanger

Only two releases exist across roughly 2 years and 7 months, with no release in the last 12 months and a median interval of about 451 days. This indicates very slow maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months. This supports the abandonment concern shown by its archived status.

Repository archiveddanger

The linked repository is archived, which is a severe abandonment risk for a dependency even though it was pushed recently. Archived projects are generally unfit for new adoption.

Build provenancecaution

The release has no build attestation or trusted-publisher provenance. That weakens publication transparency, although the repository and package contents are available for inspection.

Security policycaution

No security policy was found in the repository. This is a transparency gap, though the package's license, tests, and matching source repository provide some compensating context.