diamante/orocrm-integration-bundle

Release historydanger

The last release was about 9 years and 12 months ago, with no releases in the past 12 months. Only three releases exist, which strongly increases abandonment risk despite the stable current version.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the past 3 months, consistent with the long gap since the last release. The unarchived status does not compensate for the absence of observed maintenance.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the source relationship is not clearly established. This creates a transparency concern even though the repository owner provides organizational backing.

Repo toolingcaution

Composer is used for builds, which is appropriate, but no security-scanning tooling was detected. That is a modest hygiene gap rather than evidence of unsafe behavior.

Security policycaution

The linked repository has no security policy, leaving no documented channel or process for handling vulnerabilities. This is a meaningful transparency gap for an integration bundle.