markhuot/data

Release historydanger

The package has made no release in nearly four years; six releases arrived during its first few days, followed by prolonged silence. This is strong evidence of abandonment risk despite the stable 1.0.5 version.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no recent maintenance capacity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no meaningful community signal to offset the maintenance gap.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, though it is less serious than the lack of recent maintenance.

Workflow auditcaution

The only workflow is fully analyzed, uses read-only permissions, and has no audit findings, but both of its two action references are unpinned. That leaves avoidable build-integrity exposure without evidence of an active exploit path.