picaboooo/snapchatsdk

Release historydanger

The package has had only two releases, with none in the last 12 months; its latest release was over six years ago. This is strong evidence of abandonment for a package that depends on a changing private API.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2019. The repository is not archived, but that does not compensate for the lack of observed maintenance.

Package file treecaution

The published artifact contains 103 files, while the linked repository tree contains only two files, including the README. That makes the source and release contents difficult to verify and lowers transparency.

Repo toolingcaution

The repository reports no build tools and no security scanning. For a package handling authentication and private-API requests, the absence of these checks weakens maintenance and release confidence.

Security policycaution

No security policy is present in the linked repository. That is a transparency gap for a package whose README describes handling usernames, passwords, authentication tokens, and private API data.