safe-json-parse

Release historydanger

The latest release was about 11 years ago, with no releases in the last 12 months. This is strong evidence of inactivity, although the package has a long history and only four releases.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with a repository that has seen no commits for about 10 years and increasing abandonment risk.

Build provenancecaution

No build attestation, trusted publisher, or staged publishing is present, limiting release transparency. This is a supply-chain hygiene gap rather than evidence that the release is unsafe.

Maintainerscaution

Only one registry publishing account is listed. For this user-owned project that indicates limited publishing depth, though it is less concerning for a small, stable package.

Repo toolingcaution

The repository reports no build tooling and no security scanning, leaving fewer automated checks around future changes.