revolution/niconico

Maintainerscaution

Only one registry account can publish releases. That is a real resilience concern for this individually owned project, though the repository shows recent activity from the same maintainer.

Project backingcaution

The repository is owned by an individual rather than an organization, so the single-maintainer and concentrated-contributor risks are not buffered by visible organizational backing.

Repo bus factorcaution

One contributor made all two commits in the last three months, concentrating maintenance entirely in one person. The non-archived repository and recent release partly compensate, but do not remove the continuity risk.

Security policycaution

No repository security policy was found. For a small API client this is a transparency gap, but it is not severe enough to outweigh the active source and security tooling.

Workflow auditcaution

Both workflows grant top-level write permissions, which is broader than necessary, but the audit found no untrusted checkouts, script injection, or other findings, and all six action references are pinned. The permissions are a mild hygiene concern rather than a severe risk.