Package Health

spryker/product-labels-rest-api

This release appears suitable to depend on from a supply-chain health perspective: it has a long release history since 2018, six releases in the last 12 months, a stable non-prerelease version, active recent repository work from five contributors, organizational backing, and a matching, well-scaffolded source repository. The main concerns are the absence of repository tests, security scanning, and a SECURITY policy, plus workflow token permissions that are not explicitly restricted; these are hygiene and transparency gaps rather than evidence of abandonment. The proprietary license is accompanied by license files in both the artifact and repository, and there are no install-time lifecycle scripts or registry deprecation signals.

Latest 1.7.3PackagistPackagist

84%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

88

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

83

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

80

Health Score Breakdown

Package scaffoldingcaution

A README and changelog are present, and the repository uses GitHub Releases, but neither the artifact nor repository contains tests. For a REST API module, the missing test evidence is a genuine maintainability gap.

Repo issue activitycaution

There were no new or merged pull requests and no new or closed issues in the last month. This provides little evidence of issue responsiveness, although the null open-issue count is unknown rather than negative evidence.

Repo popularitycaution

The repository has no stars or forks and only 6 watchers, so public popularity is limited; this is supporting evidence only and is outweighed by active releases, recent commits, and organization backing.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected, leaving a security-process gap in repository hygiene.

Security policycaution

No repository security policy was found, which weakens vulnerability-reporting transparency and is a genuine repository hygiene gap.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

DependencyLast ReleaseScore
spryker/store
Version ^1.4.0
spryker/kernel
Version ^3.30.0
spryker/symfony
Version ^3.0.0
spryker/transfer
Version ^3.42.0
spryker/product-storage
Version ^1.16.0

Weekly Downloads

Info

Last Published
12 days ago
Created
7 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform