juzaweb/subscription

The registry has had no release in over two years, and the repository shows no commits or active maintainers in the last three months. Documentation, tests, release notes, and a matching source repository provide useful support, but the small project footprint and absent security scanning add uncertainty.

Latest 1.0.9

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 10 releases, but none in the last 12 months; its latest registry release was over two years ago. The earlier short median interval shows prior activity but does not offset the current gap.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last three months, providing no evidence of current maintenance capacity.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This does not prove abandonment, but it provides no recent community-maintenance signal.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. That is a modest transparency and maintenance gap rather than a standalone severe risk.

Security policy

The repository has no security policy. For a package handling subscription and payment integrations, this leaves vulnerability-reporting expectations unclear.