quick-temp

Build provenancecaution

No build attestation or trusted-publisher identity is present, so release origin is less independently verifiable. This is a transparency weakness, not evidence that the package is unsafe.

Repo commit activitycaution

The repository has no commits from active maintainers in the last three months. That suggests limited recent development activity, although the recent registry release provides some compensating evidence.

Repo issue activitycaution

There were no newly created or closed issues or pull requests in the last month, while one issue and two pull requests remain open. This indicates limited recent project interaction.

Repo popularitycaution

The repository has only 3 stars and 15 forks, indicating a small user base. Popularity is supporting evidence rather than a verdict, so this modestly lowers confidence but does not make the package unfit.

Repo toolingcaution

The repository reports no build tooling and no security-scanning tools. The small JavaScript package may not need a build system, but the absence of security scanning leaves a hygiene gap.