@handy-common-utils/dev-utils Apache-2.0 4 versions

@handy-common-utils/dev-utils

npm Repository Homepage

Utilities for the convenience of developers

Versions

Apache-2.0

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

james-hu

Keywords

handy-common-utilsdevutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Publisher has established clean track record; no material changes in this version; dormancy consistent with low-activity utility package.	ai	2026/06/02
dependencies	unvetted-dep:concat-md	AI (dependencies): Legitimate markdown utility dep for a dev-utils package; stable pattern across versions.	ai	2026/05/10
dependencies	unvetted-dep:@handy-common-utils/fs-utils	AI (dependencies): Same org/author dependency; consistent across the package's version history.	ai	2026/05/10
dependencies	unvetted-dep:serverless-plugin-git-variables	AI (dependencies): Bundled dep used for git variable extraction in dev tooling; expected for this package.	ai	2026/05/10
provenance	no-provenance	AI (provenance): Long-lived package with consistent publish history; lack of provenance is common and not a risk signal here.	ai	2026/04/30
phantom-deps	phantom-dep:typedoc-plugin-markdown	AI (phantom-deps): typedoc-plugin-markdown is a declared dep used as a typedoc plugin via config, not direct import — stable false positive for this package.	ai	2026/04/29

Versions (showing 4 of 4)

Version	Deps	Published
1.9.2	7 / 3	2026-06-01
1.9.1	7 / 3	2026-04-28
1.9.0	7 / 4	2026-04-27
1.8.0	7 / 4	2025-06-07

v1.9.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.