yawik/core

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the release history's prolonged inactivity. This materially raises the risk that defects and compatibility issues will remain unresolved.

Release historycaution

The package has 48 releases and a historically regular median interval of about 12 days, but its latest release was over five years ago and it had no releases in the last 12 months. That long silence is a meaningful maintenance and abandonment concern.

Repo popularitycaution

The repository has zero stars and forks and only two watchers. Popularity is not decisive, but these low engagement levels provide little supporting evidence of an active user or contributor community.

Repo toolingcaution

Composer is used for builds, but no security scanning tools were detected. The missing scanning is a maintenance and transparency gap, though it is less serious than the project's prolonged inactivity.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This is a genuine transparency gap for a package with a broad dependency and application-module footprint.