tudouer/simditor

Clear installation instructions, an MIT license, and no install-time scripts reduce adoption friction. No security policy or scanning, together with limited repository activity, leaves ongoing maintenance lightly evidenced.

Latest v2.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual account rather than an organization, so the small registry maintainer list is not offset by visible organizational backing.

Release history

The package has only two releases, both published about 10 minutes apart, despite being about 10.5 months old. This provides little evidence of an established maintenance cadence.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. For a package about 10.5 months old, this is meaningful evidence of limited ongoing maintenance.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. That is a modest transparency and maintenance gap.

Security policy

The repository has no security policy. This does not make the package unsafe by itself, but it leaves vulnerability reporting and response expectations undocumented.