@oslojs/encoding

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months. Combined with the absence of recent registry releases, this raises abandonment risk.

Build provenancecaution

The release has no build provenance attestation or trusted-publisher metadata. This is a transparency gap, but it is not by itself evidence that the package is unsafe to depend on.

Release historycaution

The package has had 7 releases since May 2024, with a median interval of about 18 days, but no releases in the past 12 months. The extended release gap lowers confidence in ongoing maintenance.

Repo issue activitycaution

The repository has 3 open issues and 2 open pull requests, but no issues or pull requests were newly handled in the past month. This is a modest sign of limited current activity.

Repo toolingcaution

The project uses TypeScript and npm build tooling, showing a defined build process, but no security-scanning tools were detected. The missing scanning is a minor hygiene gap.