koderhut/securitytxt

Release historydanger

Only two releases exist, with the latest published in October 2018 and none in roughly seven years and eleven months. This is strong evidence of abandonment risk for a library dependency.

Project backingcaution

The repository is owned by an organization, which provides some backing context, but the supplied activity evidence does not show that it currently supports maintenance.

Repo popularitycaution

The repository has zero stars and zero forks, with one watcher. Popularity is only supporting evidence, but these figures provide little evidence of a broader user or contributor base.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured. This is a modest transparency and maintenance gap, not a standalone severe risk.

Repository archivedcaution

The repository is not archived, which preserves a path for maintenance, but it was last pushed in October 2018. Its non-archived status does not offset the long period without updates.