azure-oss/storage

This release is usable but warrants caution. It has a stable MIT-licensed release, a non-deprecated package, an organization-backed repository, and strong recent registry release activity with 10 releases in the last 12 months. However, the linked repository shows no commits or active maintainers in the last 3 months, contains no tests, has no security scanning or security policy, and is an unusually minimal six-file metapackage. The repository README does identify the package, and the package is transparently structured as a dependency bundle, but maintenance continuity and security-process evidence are limited enough that adopters should verify the health of its transitive SDK dependencies and monitor future releases.

Latest 2.1.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README and changelog are present, and the repository uses GitHub Releases, but neither the artifact nor repository contains tests. For a metapackage this is less concerning than for executable code, though it still reduces validation evidence.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last 3 months. This conflicts with the frequent registry releases and is a meaningful continuity concern, although the recent push and release history provide partial compensation.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while issue and pull-request totals are unavailable. The absence of recent collaboration provides limited maintenance evidence and should be monitored.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning process is a transparency and supply-chain hygiene gap.

Security policy

The repository has no security policy. For a package handling Azure storage integrations, the lack of a documented vulnerability-reporting process is a genuine transparency gap.