marked-terminal

Build provenancecaution

No build attestation or trusted-publisher identity is present, limiting release transparency and making the publication process harder to verify.

Maintainerscaution

Only one registry account can publish the package, creating a thin publishing base; the repository is user-owned, so organization backing does not compensate for that risk.

Project backingcaution

The repository belongs to an individual account rather than an organization, so there is no demonstrated organizational continuity to offset the thin maintainer base.

Release historycaution

The package has existed for over 12 years with 37 releases, but it has had no registry release in the last 12 months; this indicates slowing maintenance rather than abandonment by itself.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, a meaningful sign of stalled maintenance despite the repository not being archived.