rabobank/omnikassa-sdk

Organizational backing, a recent release, tests, release notes, and a clear MIT license support continued use. Three of four workflow actions are unpinned, repository commits were absent for three months, and no security policy was found.

Latest v1.18.2

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

No commits and no active maintainers were observed in the last three months. The recent release and push provide some compensation, but the current development pause still lowers maintenance confidence.

Repo issue activity

There is one open issue and four open pull requests, with no issues or pull requests merged in the last month; this suggests limited recent interaction but is not evidence of abandonment by itself.

Repo package mention

The repository name does not match the package name and its README does not mention the package, so the linkage is less transparent even though the organization and SDK context provide some compensation.

Security policy

The repository has no security policy. This is a transparency and vulnerability-reporting gap, although it does not by itself show unsafe code.

Workflow audit

The sole workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, but three of four action references are unpinned and the workflow has no top-level permissions block. The missing block is acceptable on its own; the unpinned references are a modest supply-chain hygiene concern.