@jh-tech/util-tools-be No license 24 versions

@jh-tech/util-tools-be

npm

24

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jackhayes

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:pg	AI (phantom-deps): pg is a runtime dep used via knex config, not directly imported.	ai	2026/04/28
semgrep	semgrep:base64-decode	AI (semgrep): Decodes cursor pagination strings; no payload execution, stable pattern for this package.	ai	2026/04/28
phantom-deps	phantom-dep:eslint	AI (phantom-deps): ESLint is a dev/config dependency loaded by convention, not direct import.	ai	2026/04/28
phantom-deps	phantom-dep:axios	AI (phantom-deps): axios likely re-exported or used in config; stable false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@eslint/compat	AI (phantom-deps): Framework-scoped ESLint package loaded by convention.	ai	2026/04/28
phantom-deps	phantom-dep:eslint-plugin-n	AI (phantom-deps): ESLint plugin loaded via config, not direct import.	ai	2026/04/28
phantom-deps	phantom-dep:@eslint/eslintrc	AI (phantom-deps): ESLint config package loaded by convention.	ai	2026/04/28
phantom-deps	phantom-dep:eslint-plugin-node	AI (phantom-deps): ESLint plugin loaded via config, not direct import.	ai	2026/04/28
phantom-deps	phantom-dep:@typescript-eslint/parser	AI (phantom-deps): TypeScript ESLint parser loaded via config, not direct import.	ai	2026/04/28
phantom-deps	phantom-dep:@typescript-eslint/eslint-plugin	AI (phantom-deps): TypeScript ESLint plugin loaded via config, not direct import.	ai	2026/04/28
phantom-deps	phantom-dep:eslint-import-resolver-typescript	AI (phantom-deps): ESLint resolver loaded via config, not direct import.	ai	2026/04/28

Versions (showing 24 of 24)

Version	Deps	Published
0.0.24	22 / 3	2026-05-21
0.0.23	22 / 3	2026-05-16
0.0.22	22 / 3	2026-05-16
0.0.21	22 / 3	2026-05-16
0.0.20	22 / 3	2026-05-16
0.0.19	22 / 3	2026-05-15
0.0.18	22 / 3	2026-05-15
0.0.17	22 / 3	2026-05-10
0.0.16	22 / 3	2026-05-10
0.0.15	22 / 3	2026-05-09
0.0.14	22 / 3	2026-05-09
0.0.13	22 / 3	2026-05-09
0.0.12	22 / 3	2026-05-04
0.0.11	22 / 3	2026-05-03
0.0.10	22 / 3	2026-04-26
0.0.9	22 / 3	2026-04-26
0.0.8	22 / 3	2026-04-26
0.0.7	22 / 3	2026-04-26
0.0.6	22 / 3	2026-04-26
0.0.5	19 / 3	2026-04-25
0.0.4	19 / 3	2026-04-25
0.0.3	19 / 3	2026-04-25
0.0.2	19 / 3	2026-04-25
0.0.1	19 / 3	2026-04-25

v0.0.24

1 finding

LOW No provenance attestation provenance

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

v0.0.23

1 finding

LOW No provenance attestation provenance

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

v0.0.22

1 finding

LOW No provenance attestation provenance

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

v0.0.21

1 finding

LOW No provenance attestation provenance

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

v0.0.20

1 finding

LOW No provenance attestation provenance

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

v0.0.19

1 finding

LOW No provenance attestation provenance

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

v0.0.18

1 finding

LOW No provenance attestation provenance

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

v0.0.17

1 finding

LOW No provenance attestation provenance

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

v0.0.16

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

v0.0.13

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

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.

v0.0.9

1 finding

LOW No provenance attestation provenance

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

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

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.

v0.0.1

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.