daylerees/scientist

The repository is intact, tested, licensed, and has no open issues, but development has stopped since December 2023. Workflow dependencies are all unpinned and the project has no security policy or scanning, increasing maintenance and hygiene concerns.

Latest 2.1.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in more than three years, despite seven releases since 2016. This is a meaningful maintenance concern, though the stable 2.1.2 release and intact repository provide some compensation.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating that maintenance capacity is currently inactive.

Repo issue activity

There are no open issues and only one open pull request, with no recent issue or pull-request movement. This is mildly reassuring for backlog size but does not demonstrate active maintenance.

Repo tooling

Composer and Phing provide build tooling, but no security scanning tools were detected. This is a modest process gap rather than a standalone adoption blocker.

Security policy

The repository has no security policy, leaving disclosure and response expectations undocumented. The gap lowers transparency but is not severe on its own.