treast/behat-fixture-bridge

Maintainerscaution

Only one registry account has publishing access. That is not inherently unhealthy for a user-owned project, but it leaves a thin publishing base if the maintainer becomes unavailable.

Release historycaution

The package has only three releases and was first published today, with releases arriving within minutes of one another. This shows active initial publishing but provides no longer-term maintenance record.

Repo commit activitycaution

There were no commits or active maintainers during the last three months, but the repository was created or updated today, so the metric reflects the package's very short history rather than a demonstrated collapse in maintenance.

Repo popularitycaution

The repository has zero stars, forks, and watchers. This is understandable for a package published today, but it provides no independent adoption evidence yet.

Security policycaution

The repository has no security policy. This is a transparency gap for reporting vulnerabilities, though it is less significant for a small package with no established user base.