permiakov/oauth2-eloqua

Release historydanger

The package has had no release in roughly 9 years and 9 months, with only three releases total and none in the last 12 months. This is strong evidence of abandonment risk for a dependency tied to an external service.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with its last push occurring in January 2017. There is no observed maintenance capacity for new compatibility or security issues.

Repo issue activitycaution

One issue remains open, with no issues or pull requests created or closed in the last month. This adds modest uncertainty about whether reported problems receive attention.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. That limits evidence of automated vulnerability oversight for future changes.

Security policycaution

The repository has no security policy, so there is no stated process for reporting or handling vulnerabilities. This is a transparency gap, though the package is small and has a simple dependency profile.