creonit/verification-code-bundle

Release historydanger

The package has had no release in more than six years: only three releases, all in 2020, with none in the last 12 months. This is strong evidence of abandonment risk for a framework bundle.

Repo issue activitycaution

There were no new or closed issues or pull requests in the measured one-month window. This is consistent with the wider maintenance gap, though the short window alone is limited evidence.

Repo package mentioncaution

The repository name does not match the full package name and its README does not mention the package. A sub-package naming difference can be normal, but the lack of a README reference makes package ownership less transparent.

Repo popularitycaution

The repository has zero stars and two forks. Popularity is only supporting evidence, but this provides little external evidence of active adoption or community oversight.

Security policycaution

The repository has no security policy. That does not prove a security problem, but it reduces transparency for reporting and handling vulnerabilities in a package that processes verification codes.