ttree/jsonstore-newsletterreveiversource

Release historydanger

The latest release was published in January 2018, about 8 years and 8 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having two historical releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. The repository is not archived, but there is no observed recent maintenance to offset the inactivity.

Repo package mentioncaution

The repository name matches the package, reducing the risk of an unrelated source repository, but the README does not mention the package explicitly. That weakens source transparency slightly.

Repo popularitycaution

The repository has zero stars and zero forks, with two watchers. This offers little supporting evidence of broad adoption, but popularity is only secondary evidence and does not determine health by itself.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a minor hygiene gap, not a standalone reason to reject the package.