mead-steve/mon-work-go

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement identified. This is a severe adoption risk even though the linked repository is not archived.

Release historydanger

The package has had only five releases, all concentrated in 2014, with no releases in the last 12 months. That long release gap strongly indicates abandonment.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and limited evidence of ongoing maintenance.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are present. This is a secondary transparency gap in an otherwise very old project.

Security policycaution

The linked repository has no security policy. This weakens vulnerability-reporting transparency, although it is secondary to the package's abandonment signals.