json2mq

Release historydanger

Only two releases exist, with the latest published in January 2015 and none in nearly 12 years. This strongly lowers confidence in ongoing maintenance, though the package may be stable for its narrow purpose.

Repo commit activitydanger

There were no commits or active maintainers in the last 3 months, consistent with a repository that has seen no push in nearly 8 years. This is a substantial abandonment-risk signal.

Project backingcaution

The repository is owned by an individual rather than an organization, so there is no organizational backing shown to offset the thin maintenance history.

Repo toolingcaution

The repository uses no build or security-scanning tooling. For this six-file, direct JavaScript package, the lack of build tooling is expected, but the absence of security scanning leaves less verification coverage.

Security policycaution

No repository security policy is present. This is a transparency gap, though it is less consequential for a small utility with a minimal dependency surface.