@oslojs/jwt

Registry deprecationdanger

The package is deprecated at npm with a package-wide message stating it is no longer supported and no replacement listed, making this release unfit for a new dependency.

Release historydanger

Only three releases have been published, with none in the last 12 months; the latest release was nearly two years before collection, indicating prolonged inactivity.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, providing no evidence 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 not the primary reason for the low score.

Workflow auditcaution

The sole workflow was fully analyzed without untrusted triggers or injection findings, but both action references are unpinned and it installs a package outside a lockfile, creating release-workflow hygiene concerns.