bviguier/siglot

Release historydanger

This is the only release, published about two years ago, with no releases in the last 12 months. That leaves little evidence of ongoing maintenance despite the repository remaining available.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the single-release history, this is strong evidence of an inactive project.

Repo toolingcaution

The project uses Make and Composer, but no security scanning tools were detected. That is a modest transparency and maintenance gap for a dependency project.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less severe for a small, inactive package than an archived or deprecated release.

Version stabilitycaution

Version 0.1.0 is not a stable major release, so the public API may still change. The absence of prerelease labeling does not offset the package's early maturity.