copyfiles

Release historydanger

The package has 18 releases but none in the last 12 months; its latest registry release was in November 2020. This is a significant maintenance and abandonment concern.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Together with the old registry release, this indicates sharply limited current maintenance.

Build provenancecaution

No build attestation or trusted-publisher identity is present, leaving publication provenance less transparent. This is a supply-chain hygiene gap rather than evidence that the release is unsafe.

Dependency profilecaution

Seven runtime dependencies are a moderate footprint for a small CLI utility and add some maintenance surface, but the count alone does not indicate a serious problem.

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base and increases continuity risk, although repository activity is the stronger evidence of maintenance capacity.