os-filter-obj

Release historydanger

The latest registry release was in July 2017, with no releases in the last 12 months; this is a substantial maintenance and abandonment concern for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months. Combined with the old latest release, this indicates weak current maintenance capacity.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, limiting release transparency; this is a hygiene gap rather than evidence that the release is unsafe.

Maintainerscaution

Only one registry maintainer is listed. That is a limited publishing bus factor for a user-owned project, though the package is small and the repository is clearly linked to the same owner.

Project backingcaution

The repository is owned by an individual account rather than an organization, so there is no organizational backing to compensate for the thin maintainer base.