bplist-parser

Maintainerscaution

Only one registry account has publish access. This is a resilience concern because a single publisher creates a limited operational fallback, though repository activity and backing evidence provide some compensation.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no organizational continuity signal. This reinforces the single-maintainer resilience concern but does not establish abandonment.

Repo commit activitycaution

No commits and no active maintainers were recorded in the last 3 months, which is a genuine maintenance slowdown. This is partly offset by the recent repository push, release, and merged pull-request activity, so it is caution rather than danger.

Repo toolingcaution

The repository uses TypeScript and a build tool, supporting reproducible project structure, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than a standalone severe risk.

Security policycaution

The repository has no security policy. This reduces transparency around vulnerability reporting and response, though it does not by itself indicate that the package is unsafe to use.