safe-stable-stringify

Build provenancecaution

No build attestation or trusted-publisher provenance is provided, leaving publication origin less transparent. This is a supply-chain transparency gap rather than evidence that the release is unsafe.

Maintainerscaution

Only one registry publishing account is listed, which creates a thin publishing base. The repository is user-owned rather than organization-owned, so there is no provided backing signal to compensate for that concentration.

Release historycaution

The package has 14 releases over about 8 years, but none in the last 12 months and the latest registry release was over two years ago. This is a meaningful maintenance concern, despite the historically regular median release interval of about 71 days.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. This indicates currently inactive development and materially increases abandonment risk, even though the repository is not archived.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while three issues and four pull requests remain open. This suggests limited recent project activity.