@oslojs/binary

Registry deprecationdanger

The entire package is marked deprecated with no replacement, which directly indicates that it is no longer supported and makes this release unfit for a new dependency.

Release historydanger

The package has had no release in over 18 months, despite 10 releases during its earlier development period. This supports the conclusion that active package delivery has stopped.

Build provenancecaution

No build attestation or trusted-publisher provenance is available, so consumers cannot verify how the published artifact was produced. This weakens supply-chain transparency but is not independently decisive.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the lack of current maintenance capacity.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, though it is secondary to the package deprecation.