@oslojs/crypto

Registry deprecationdanger

The registry marks the entire package as deprecated with the message “Package no longer supported,” and provides no replacement. This is a decisive adoption risk even though other project signals are positive.

Release historydanger

The package has 16 releases since May 2024, but its latest release was in September 2024 and it had no releases in the last 12 months. The earlier rapid cadence does not compensate for the prolonged publishing gap.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last three months. This indicates the project is not currently receiving maintenance, despite the repository remaining unarchived.

Build provenancecaution

No build attestation or trusted-publisher provenance is present. This reduces publication transparency, although it is secondary to the explicit package deprecation.

Repo toolingcaution

The repository uses TypeScript and npm build tooling, but no security-scanning tools were detected. For a cryptographic library, the missing scanning layer is a modest maintenance and assurance gap.