Package Health

spryker/symfony

Healthy and suitable to depend on. It has a long release history, a recent stable release, active work from five contributors, and complete package and repository documentation; the main caveat is limited repository security-policy and workflow-permission hardening.

Latest 3.21.0PackagistPackagist

84%

Total Score

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

100

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

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

94

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

80

Health Score Breakdown

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool is configured. This is a modest transparency and preventive-maintenance gap, not evidence of abandonment.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unspecified. The gap lowers transparency, although active releases and maintained source provide some compensation.

Token permissionscaution

The CI workflow does not declare top-level token permissions. It has no observed top-level write permissions, but the missing explicit restriction leaves avoidable workflow hardening undone.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

DependencyLast ReleaseScore
symfony/form
Version ^6.4.0 || ^7.4.0
—
—
symfony/intl
Version ^6.4.0 || ^7.4.0
—
—
symfony/lock
Version ^6.4.0 || ^7.4.0
—
—
symfony/mime
Version ^6.4.0 || ^7.4.0
—
—
symfony/yaml
Version ^6.4.0 || ^7.4.0
—
—

Weekly Downloads

Info

Last Published
15 days ago
Created
10 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