Package Health/openmage-strict/module-persistent

openmage-strict/module-persistent

The repository has no security policy or security scanning, which weakens transparency. Organization backing, a matching repository, a license, and a GitHub release provide useful context.

Latest 120.2.0

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published about 2 years and 10 months ago, with no releases in the last 12 months. This is a meaningful maintenance concern, though the linked repository was pushed more recently.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the past 3 months, indicating no recent development activity. This raises maintenance risk despite the repository not being archived.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest supply-chain hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for a package used in an application framework.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
openmage-strict/module-checkout Version ^120.2	—	—
openmage-strict/module-adminhtml Version ^120.2	—	—
magento-hackathon/magento-composer-installer Version *	—	—