oxygen/mod-events

Release historydanger

The package has 31 releases since 2015, but none in the last 12 months; its latest release was about 4 years and 6 months ago. The long historical release record helps, but does not offset the current inactivity.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release gap and indicating little current maintenance capacity.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem. No security scanning tools were detected, a transparency gap, but the repository's prolonged inactivity is the more important concern.

Security policycaution

The repository has no security policy, reducing transparency around vulnerability reporting. This is a hygiene concern rather than evidence that the package is unfit on its own.

Token permissionscaution

The one workflow does not declare top-level token permissions, so its permissions are less explicit than recommended. No top-level write permissions were observed, limiting the severity of this gap.