alex-kalanis/nested-tree-nette

Project backingcaution

The package and repository are owned by the same individual account, with no organization backing shown. This is a modest bus-factor concern rather than a severe issue when combined with the release history.

Repo commit activitycaution

No commits or active maintainers were recorded in the past 3 months. This is a meaningful maintenance warning, despite the recent release and repository push evidence.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a repository hygiene gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy. This weakens vulnerability-reporting transparency for a package that integrates with a database framework.

Workflow auditcaution

The single workflow was fully analyzed with no dangerous triggers or audit findings, but all 8 action references are unpinned. That leaves build inputs less reproducible and increases maintenance hygiene risk.