riddlestone/brokkr-gulpfile

Release historydanger

The package has had no registry release in more than six years, despite five releases early in its history. That long gap is strong evidence of reduced maintenance capacity.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the extended release gap and increasing abandonment risk.

Repo issue activitycaution

There has been no issue or pull-request activity in the last month, with one issue still open; this provides little evidence of current support.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than decisive, but these figures do not provide external evidence of ongoing use.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, not evidence that the package is unsafe.