common-gateway/open-belasting-bundle

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the long gap since the last push. This is strong evidence of abandonment risk.

Release historycaution

The package has 41 releases, but none in the last 12 months and the latest release was published about two and a half years ago. The earlier release history shows past activity but does not offset the current maintenance gap.

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 demonstrated. This is a transparency concern even though organization-owned monorepo subpackages can have different names.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a hygiene gap rather than proof that the package is unsafe.

Security policycaution

The repository has no security policy, reducing transparency about how vulnerabilities are reported and handled. The organization backing provides some context but does not replace a published process.