@yuants/utils No license 39 versions

@yuants/utils

npm

39

Versions

—

License

No

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

zccz14ntnl-infra

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): Well-known crypto/date libraries matching package's utility scope.	ai	2026/07/09
semgrep	semgrep:base64-decode	AI (semgrep): Standard base64 utility function, no malicious payload.	ai	2026/07/09
semgrep	semgrep:hex-decode	AI (semgrep): Standard hex utility function, no malicious payload.	ai	2026/07/09
dependencies	unvetted-dep:@yuants/prometheus	AI (dependencies): First-party sibling package from same publisher/monorepo.	ai	2026/07/09

Versions (showing 39 of 39)

Version	Deps	Published
0.19.7	8 / 9	2026-03-18
0.19.6	8 / 9	2026-02-07
0.19.5	8 / 9	2026-01-26
0.19.4	8 / 9	2026-01-06
0.19.3	8 / 9	2026-01-02
0.19.2	8 / 9	2026-01-01
0.19.1	8 / 9	2025-12-31
0.19.0	8 / 9	2025-12-28
0.18.0	8 / 9	2025-12-24
0.17.0	8 / 9	2025-12-23
0.16.0	8 / 9	2025-12-23
0.15.0	8 / 9	2025-12-16
0.14.0	8 / 9	2025-11-29
0.13.0	8 / 9	2025-11-25
0.12.0	7 / 9	2025-11-24
0.11.0	7 / 9	2025-11-10
0.10.1	7 / 9	2025-11-10
0.10.0	7 / 9	2025-10-21
0.9.0	7 / 9	2025-10-19
0.8.0	6 / 9	2025-09-16
0.7.1	6 / 9	2025-09-04
0.7.0	6 / 9	2025-09-02
0.6.0	5 / 8	2025-08-23
0.5.0	5 / 8	2025-08-05
0.4.1	5 / 8	2025-08-01
0.4.0	5 / 8	2025-07-11
0.3.8	3 / 8	2025-04-21
0.3.7	3 / 8	2025-01-14
0.3.6	3 / 8	2025-01-13
0.3.5	3 / 8	2025-01-13
0.3.4	3 / 8	2025-01-13
0.3.3	3 / 8	2025-01-08
0.3.2	3 / 8	2024-12-19
0.3.1	3 / 8	2024-09-09
0.3.0	3 / 8	2024-09-08
0.2.1	3 / 8	2024-09-04
0.2.0	3 / 8	2024-08-30
0.1.0	1 / 8	2024-07-12
0.0.6	1 / 8	2024-02-22

v0.19.7

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2026-03-18, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2026-03-18, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.19.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2026-02-07, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2026-02-07, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.19.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2026-01-26, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2026-01-26, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.19.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2026-01-06, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2026-01-06, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.19.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2026-01-02, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2026-01-02, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.19.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2026-01-01, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2026-01-01, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.19.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2025-12-31, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2025-12-31, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.19.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2025-12-28, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2025-12-28, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.18.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2025-12-24, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2025-12-24, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.17.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2025-12-23, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2025-12-23, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.16.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2025-12-23, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2025-12-23, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.15.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ntnl-infra → zccz14 (on 2025-12-16, known maintainer) provenance

This version was published by a different npm account (zccz14) than the most recent previously approved version (ntnl-infra) on 2025-12-16, but zccz14 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.6

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.