jasirilabs/nanasisms

The source project has tests, a changelog, and an MIT license, with organization backing and no install-time scripts. Its release and commit history is stale enough to make long-term maintenance a significant concern, while workflow references are not pinned.

Latest v0.1.3

Packagist

48%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was over four years ago, with no releases in the last 12 months. The six releases were initially frequent, but the prolonged gap is a substantial maintenance concern.

Repo commit activity

There were no commits or active maintainers in the last three months. Combined with the old latest release, this materially raises abandonment risk.

Repo issue activity

There was no issue or pull-request activity in the last month, with one issue still open. This is consistent with a quiet project and adds modest maintenance concern.

Repo tooling

The repository uses Composer, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe by itself.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency and maintenance gap, though it is not decisive alongside the available project evidence.