m12/flow-rollbar

Clear documentation, tests, an MIT license, and release notes support adoption basics. The missing security policy and very small project footprint add transparency concerns, while compatibility with current Flow/Neos versions should be verified separately.

Latest v0.3.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has four releases, all concentrated between October 20 and October 25, 2016, with no release in roughly 10 years. That is strong evidence of abandonment for a dependency receiving ongoing production use.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push having been in December 2018. This leaves little evidence of current maintenance capacity.

Dependency profile

Four runtime dependencies, including Flow/Neos components and the Rollbar client, create compatibility and maintenance exposure for an old integration package. The count is modest, but the stale release history makes those dependencies more consequential.

Project backing

The repository is owned by an organization, which provides some backing context, but the observed release and commit activity shows no current maintenance. Organizational ownership therefore does not compensate for the stale project history.

Repo issue activity

There has been no new or closed issue or pull request activity in the last month, with one issue still open. This reinforces the lack of recent project attention, although it is weaker evidence than the stalled release and commit history.