pkc/video-call

The README and MIT declaration make the package understandable and legally usable, while its small dependency set limits complexity. Maintenance evidence is weak: all three releases arrived in one brief burst, with no commits in the past three months and no security policy or scanning.

Latest v1.0.2

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months. Combined with the old latest release, this is concrete evidence of stalled maintenance.

Maintainers

Only one registry account has publish access, leaving little visible publishing redundancy. The repository is user-owned rather than organization-backed, so there is no provided organizational backing to offset this concern.

Release history

The package has had three releases, all clustered around May 23, 2025, followed by about 16 months without a release. That short burst and long quiet period raise maintenance concerns.

Repo popularity

The repository has one star and one fork, indicating a very small adoption footprint. Popularity is supporting evidence only, but it provides little external confidence for a package handling real-time calling.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That weakens assurance for a package with browser and signaling components, though it is not evidence of a defect.