wwardaww/insert-on-duplicate-key

Release historydanger

The package has had no release in more than eight years, with zero releases in the last 12 months. Its 20-release history shows initial activity but does not compensate for the prolonged pause.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old last release, this is strong evidence of abandonment risk.

Project backingcaution

The repository is owned by the same individual namespace as the package, with no organization backing shown. This is consistent ownership but provides limited maintenance capacity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little community backing or independent adoption evidence. Popularity is supporting evidence, so this reinforces rather than determines the maintenance concern.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a modest transparency gap for a package with otherwise simple structure.