sanjokdangol/apicall

Maintainerscaution

Only one registry maintainer is listed. That is consistent with a personal project but leaves little visible publishing redundancy if the maintainer becomes unavailable.

Release historycaution

The package is about 8 months old but has only one release, with no follow-up version after the initial v0.1.0. That is meaningful evidence of limited maturity for a dependency.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last 3 months. For a young package, that weakens evidence of ongoing maintenance, although it does not by itself prove abandonment.

Repo popularitycaution

The repository has 2 stars, no forks, and no watchers. This is weak supporting evidence of adoption, but popularity alone does not determine whether a small package is healthy.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are reported. That is a hygiene gap rather than a direct dependency risk.