artflow-studio/tenancy

Usable with caveats: the package has regular releases, substantial documentation, tests, and an active-looking unarchived repository, but the repository recorded no commits or active maintainers in the last three months. Its lack of security tooling and a security policy adds maintenance transparency risk.

Latest 0.8.4

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace is Artflow Studio but the repository is owned by an individual account, so organizational backing is not established; this provides limited assurance about long-term support.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months, which is a meaningful maintenance concern for a package that handles database isolation and framework integration.

Repo popularity

The repository has zero stars, forks, and watchers, providing no community adoption evidence; popularity is supporting evidence, so this lowers confidence more than it lowers health by itself.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That leaves an avoidable transparency and maintenance gap for a package with database and infrastructure responsibilities.

Security policy

The repository has no security policy, so users have no documented path for reporting vulnerabilities or understanding security response practices.