beriyack/jamfapi

Release historycaution

There have been only two releases, both within roughly 1 hour and 40 minutes on the first release day, with no later release over the package's roughly 11-month lifetime. That gives little evidence of sustained maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. With the last push roughly 11 months ago, this is meaningful abandonment risk for a library integration.

Repo package mentioncaution

The repository name does not match beriyack/jamfapi, and its README does not mention the package name. Although the source tree appears related, consumers cannot verify the package relationship from the repository documentation.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tool is configured. The missing scanning is a modest transparency and maintenance gap.

Repository archivedcaution

The linked repository is not archived, but its last push was roughly 11 months ago, consistent with the absence of recent maintenance evidence.