dashed/dashed-omnisocials

This release appears suitable to depend on, with strong evidence of active development and reasonable project maturity: it has 24 stable releases over 141 days, a current non-archived repository, organizational backing, tests and changelog coverage, and a modest runtime dependency set. The main concerns are limited repository activity in the last three months, the absence of a security policy and security-scanning tooling, and no README in the package or repository metadata; these reduce transparency and assurance but do not outweigh the otherwise healthy maintenance signals.

Latest v4.4.1Packagist

Health Score Breakdown

Repo commit activitycaution

The repository recorded three commits in the last three months from two active maintainers. Activity is present but relatively light, so it provides only moderate evidence of ongoing maintenance.

Repo toolingcaution

Composer build tooling is used, supporting reproducible package management. No security-scanning tools are configured, leaving a modest assurance gap for supply-chain hygiene.

Security policycaution

The repository has no security policy. This weakens vulnerability-reporting and maintenance transparency, though it is not by itself evidence of unsafe code or abandonment.

View all 18 health checks

Vulnerabilities

We didn't find any vulnerabilities for this package.

Maintainers

Robin van Maasakker

Direct Dependencies

Dependency	Last Release	Score
dashed/dashed-core Version *	—	—
dashed/dashed-marketing Version *	—	—
spatie/laravel-package-tools Version ^1.16	—	—