slacker775/concur-api

The MIT license, clear package identity, and README make the project understandable to adopt. Its small audience and missing security policy add little reassurance for a client library; pin this version only if you can maintain it yourself.

Latest 1.0.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. For this user-owned project that is a narrow publishing base, and the inactive repository provides no evidence of broader maintenance capacity.

Release history

The package has had no release in nearly seven years: its latest release was in November 2019, with zero releases in the last 12 months. This is strong evidence of abandonment risk despite the three-release history.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.

Repo popularity

The repository has zero stars and forks and only one watcher, so there is little community evidence to compensate for the inactive maintenance history.

Security policy

The repository has no security policy, which reduces transparency for a client library handling authentication and API credentials. This is a hygiene gap rather than evidence of unsafe code.