gourmet/dashboard

Release historydanger

The package has only three releases, all clustered in 2014, with zero releases in the last 12 months and a package age of about 12 years. This is strong evidence of abandonment for a dependency.

Repository archiveddanger

The repository is not formally archived, but its last push was in February 2015, nearly 12 years before assessment. That observed inactivity is a substantial maintenance risk despite the repository remaining available.

Project backingcaution

The repository is owned by the gourmet organization, which provides some project backing. However, that administrative context does not compensate for the observed absence of release and commit activity.

Security policycaution

The repository has no security policy. This is a transparency and maintenance gap, though it is secondary to the much stronger evidence of prolonged inactivity.

Version stabilitycaution

Version 0.2.0 is not a stable major release, and the registry's latest version is 0.1.1, suggesting an immature or inconsistent release line. The lack of recent releases reinforces that concern.