parse-imports

Build provenancecaution

No build attestation or trusted-publisher provenance is present, reducing release transparency. This is a supply-chain transparency gap but not by itself evidence that the release is unsafe.

Maintainerscaution

Only one registry publishing account is listed, and the repository owner is an individual rather than an organization. This creates a meaningful bus-factor concern, although repository activity and tests provide some compensation.

Project backingcaution

The repository is owned by an individual account, so there is no organization backing to offset the single-publisher and single-maintainer profile.

Release historycaution

The package has existed since June 2020 with 16 releases, but none were published in the last 12 months; the latest release was about 1 year ago. This indicates slowed maintenance despite a reasonable historical cadence.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly year-long release gap and raising abandonment risk.