szagot/config

Release historydanger

The package has had only two releases, with the latest published in January 2018 and none in the last 12 months. This is strong evidence of prolonged release inactivity for a dependency.

Licensecaution

No license declaration or license file was detected in the package or repository. That creates a real transparency and reuse concern for an open-source dependency.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, despite the latest repository push being in November 2024. This provides little evidence of current maintenance.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tool is present. The missing scanning is a minor hygiene gap rather than decisive evidence on its own.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a modest transparency gap alongside the weak maintenance evidence.