Package Health

oblak/extremis

The package includes a readable guide and its repository clearly matches the package. It also lacks a security policy and automated security scanning, adding transparency concerns.

Latest 1.1PackagistPackagist

32%

Total Score

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

50

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

64

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

50

Health Score Breakdown

Licensedanger

The manifest declares the package as Closed, with no detected license text or license file. That is a serious adoption and redistribution concern for an open-source dependency.

Release historydanger

Only two releases were published, both in January 2021, with no releases in the last 12 months. This indicates a long period without release maintenance.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the absent recent releases, this supports a substantial abandonment concern.

Lifecycle scriptscaution

Composer install-time scripts run post-autoload-dump and post-create-project-cmd. These can be legitimate project setup behavior, but they increase the review surface for consumers.

Repo toolingcaution

Composer is used as a build tool, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

DependencyLast ReleaseScore
oblak/extremis-core
Version ^2.0
oblak/wp-asset-manager
Version ^2.0

Weekly Downloads

Info

Last Published
5 years ago
Created
5 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