aggrego/neo4j-integration

Release historydanger

Only one release exists, published about 7 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and indicating no current maintenance capacity.

Repo popularitycaution

The repository has 0 stars and 0 forks, offering no supporting evidence of broad use or community participation. Popularity is secondary, but this reinforces the thin project footprint.

Repository archivedcaution

The repository is not archived, which avoids the strongest abandonment signal, but its last push was about 7 years ago and does not offset the lack of recent activity.

Security policycaution

The repository has no published security policy. This is a transparency gap, though it is less significant than the package's prolonged inactivity.