securetrading/data

The small, focused package has clear documentation, tests, minimal dependencies, and organization backing. Its long release gaps and limited repository safeguards leave more maintenance uncertainty than a mature dependency should.

Latest 3.0.2

Packagist

66%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed since 2016 and released once in the last 12 months, but its median release interval is about 768 days, indicating a slow maintenance cadence.

Repo commit activity

There were no commits and no active maintainers in the three months before collection. The recent release shows some current activity, but does not remove the concern about a thin ongoing development signal.

Repo package mention

The repository name does not exactly match securetrading/data and its README does not mention the package. This may be a subpackage naming difference, but the lack of either linkage signal warrants caution about source-package correspondence.

Repo tooling

Composer is used for builds, but no security scanning tool is configured, leaving automated detection coverage unclear.

Security policy

The repository has no security policy, so its process for receiving and disclosing vulnerabilities is not documented.