jsila/datum

Release historydanger

Only one release exists, published about 12 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency intended for ongoing use.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last release, this materially increases abandonment risk.

Project backingcaution

The repository and registry package are owned by the same individual account, so the source relationship is coherent. There is no organizational backing shown to offset the single-person maintenance risk.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide no meaningful community backing to compensate for inactivity.

Repo toolingcaution

The repository uses Composer, but no security-scanning tools were detected. The small, old package is not made unsafe by this alone, though transparency and maintenance checks are limited.