gravatalonga/configuration-scan

Release historydanger

The package has one release, published in January 2022, and none in the following four years. That long period without a new release raises abandonment risk, even for a small stable package.

Repo commit activitydanger

There were no commits and no active maintainers in the past three months, consistent with a project that has not been maintained since its initial release. This materially increases abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. This is a modest repository-hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy. For a small package this is a transparency gap, though it is less significant than the prolonged lack of development activity.

Workflow auditcaution

The single workflow was fully analyzed with no dangerous triggers or audit findings, but all three action references are unpinned. That leaves the build exposed to moving action revisions and is a release-hygiene concern.