Package Health

naas/user

Its MIT license and only two runtime dependencies reduce adoption friction. The repository has just two files, no README, and no release for over two years, making this a maintenance liability.

Latest 1.0.4PackagistPackagist

43%

Total Score

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

50

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

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

69

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

50

Health Score Breakdown

Release historydanger

All three releases arrived within minutes on 2024-02-16, followed by no releases in the last 12 months; this strongly suggests the project is no longer maintained.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the long gap since the initial release burst.

Package file treecaution

Both the package and repository contain only .gitignore and composer.json, leaving little visible implementation or project documentation.

Package scaffoldingcaution

Release notes exist for version 1.0.4, but the package has no README; tests and a changelog are not expected in the published artifact.

Repo toolingcaution

Composer is used for builds, but no security-scanning tooling is present; this is a modest transparency and hygiene gap for a dependency project.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Nuno Armando

Direct Dependencies

DependencyLast ReleaseScore
naas/setting
Version 0.1.* || @dev

Weekly Downloads

Info

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