viget/craft-disqus-notify

Release historydanger

Only two releases exist, with the latest published in January 2019 and none in the past 12 months. This is strong evidence of a long-dormant release process.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the repository having been inactive since January 2019. This materially raises abandonment and compatibility risk.

Repo popularitycaution

The repository has one star and no forks, indicating limited adoption evidence. Popularity is only supporting evidence, so this modestly lowers confidence in project maturity rather than deciding the score.

Repo toolingcaution

Composer is used for the build, but no security scanning tooling is present. The missing scanning is a hygiene gap, while the simple Composer-based build limits its practical impact.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This is a transparency gap, though it is less important than the long-standing inactivity.