Package Health

spryker-eco/google-analytics

This is a usable, organization-backed package with a stable 1.3.0 release, four releases over 120 days, a matching and clearly identified source repository, tests, CI tooling, and no deprecation or archived-repository indicators. However, the package is still relatively young, repository commit activity reports no commits or active maintainers in the last three months, repository popularity is currently zero, and the repository lacks security scanning, a security policy, and explicit top-level workflow permissions. These are meaningful transparency and maintenance risks, but not enough on the available evidence to make the package unfit to adopt.

Latest 1.3.0PackagistPackagist

68%

Total Score

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

83

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

Release historycaution

The package is young at 120 days old but has four releases, all within the last 12 months, with a median interval of about 12 days. That indicates active initial publication, though it does not yet demonstrate long-term maintenance.

Repo commit activitycaution

The repository reports zero commits and zero active maintainers over the last three months, despite a recent push and release activity. This inconsistency weakens confidence in sustained maintenance and is the strongest abandonment concern in the supplied signals.

Repo popularitycaution

The repository has zero stars, forks, and watchers. This provides no supporting adoption evidence, although the package is only 120 days old and organization backing compensates for the lack of popularity to some extent.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are detected. The build setup is adequate for a PHP package, while the missing security automation is a genuine hygiene gap.

Security policycaution

The repository has no security policy. This reduces vulnerability-reporting transparency, though it is a governance gap rather than evidence that the package is unsafe to depend on.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

DependencyLast ReleaseScore
google/gax
Version ^1.0.0
—
—
spryker/gui
Version ^5.5.0
—
—
spryker/log
Version ^3.0.0
—
—
spryker/store
Version ^1.28.0
—
—
spryker/kernel
Version ^3.46.0
—
—

Weekly Downloads

Info

Last Published
29 days ago
Created
5 months 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