@oslojs/asn1

Registry deprecationdanger

The registry marks the entire package as deprecated with the message “Package no longer supported” and provides no replacement, making this release unfit for a new dependency.

Maintainerscaution

Only one registry account has publish access. That is not inherently unhealthy for an organization-backed project, but it leaves little visible publishing redundancy alongside the lack of recent activity.

Release historycaution

The package has had no releases in the last 12 months, despite being 840 days old; its nine releases were concentrated early in its history, which supports the abandonment concern.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, so there is no observed recent maintenance to offset the package deprecation.

Repo toolingcaution

The project uses TypeScript and npm build tooling, showing a defined build process, but no security-scanning tools were detected, limiting security-process evidence.