amberovsky/time

Release historydanger

The package has had only two releases and none in over six years, with no releases in the last 12 months. This strongly raises abandonment risk, despite the package being small and stable.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, while the repository was last pushed over six years ago. This is strong evidence that maintenance has stopped.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, offering little evidence of external adoption or community support. Popularity is supporting evidence, but this adds to the maintenance concern.

Repo toolingcaution

The repository uses Make and Composer, showing basic build discipline, but it has no security-scanning tooling. The missing scanning is a modest transparency and maintenance gap.

Security policycaution

The linked repository has no security policy. For a small utility this is not severe on its own, but it leaves vulnerability-reporting expectations unclear.