jh-be-tools ISC 45 versions

jh-be-tools

npm

There is a version mismatch between packages (usually zod or express) use: npm ls zod express @types/express to find the versions

45

Versions

ISC

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 — 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:eslint	AI (phantom-deps): ESLint is intentionally exported via ./eslint.config.mjs; legitimate dependency for this package's public API.	ai	2026/04/25
phantom-deps	phantom-dep:@eslint/compat	AI (phantom-deps): Framework-scoped ESLint package; part of exported ESLint configuration API.	ai	2026/04/25
phantom-deps	phantom-dep:eslint-plugin-n	AI (phantom-deps): Referenced in exported ESLint config; intentional dependency for this package's tooling exports.	ai	2026/04/25
phantom-deps	phantom-dep:@eslint/eslintrc	AI (phantom-deps): Framework-scoped ESLint package; part of exported ESLint configuration.	ai	2026/04/25
phantom-deps	phantom-dep:eslint-plugin-node	AI (phantom-deps): Referenced in exported ESLint config; intentional dependency for this package's tooling exports.	ai	2026/04/25
phantom-deps	phantom-dep:@typescript-eslint/parser	AI (phantom-deps): Referenced in exported ESLint config; intentional dependency for TypeScript linting support.	ai	2026/04/25
phantom-deps	phantom-dep:@typescript-eslint/eslint-plugin	AI (phantom-deps): Referenced in exported ESLint config; intentional dependency for TypeScript linting support.	ai	2026/04/25
phantom-deps	phantom-dep:eslint-import-resolver-typescript	AI (phantom-deps): Referenced in exported ESLint config; intentional dependency for import resolution.	ai	2026/04/25

Versions (showing 45 of 45)

Version	Deps	Published
1.0.96	19 / 4	2026-04-25
1.0.95	18 / 3	2026-04-25
1.0.94	18 / 3	2026-04-25
1.0.92	18 / 3	2026-04-19
1.0.91	18 / 3	2026-04-19
1.0.87	18 / 3	2026-04-19
1.0.86	17 / 3	2026-04-11
1.0.85	17 / 3	2026-01-31
1.0.84	17 / 3	2026-01-31
1.0.83	17 / 3	2026-01-31
1.0.82	17 / 3	2026-01-31
1.0.81	0 / 3	2026-01-30
1.0.80	0 / 3	2026-01-26
1.0.79	0 / 3	2026-01-26
1.0.78	0 / 3	2026-01-26
1.0.77	0 / 3	2025-11-02
1.0.76	0 / 3	2025-11-01
1.0.75	0 / 3	2025-09-19
1.0.74	0 / 3	2025-09-19
1.0.73	0 / 3	2025-09-17
1.0.72	0 / 3	2025-09-17
1.0.71	0 / 3	2025-09-17
1.0.70	0 / 3	2025-09-17
1.0.69	0 / 3	2025-09-17
1.0.68	0 / 3	2025-09-17
1.0.67	0 / 3	2025-09-17
1.0.66	0 / 3	2025-09-17
1.0.65	0 / 3	2025-09-17
1.0.64	0 / 3	2025-09-17
1.0.63	0 / 3	2025-09-17
1.0.62	0 / 3	2025-09-17
1.0.61	0 / 3	2025-09-17
1.0.60	0 / 3	2025-09-17
1.0.59	0 / 3	2025-08-16
1.0.58	0 / 3	2025-07-20
1.0.57	0 / 3	2025-07-20
1.0.56	0 / 3	2025-07-13
1.0.55	0 / 7	2025-07-13
1.0.54	0 / 7	2025-07-13
1.0.53	0 / 7	2025-07-07
1.0.52	4 / 7	2025-07-06
1.0.51	3 / 6	2025-06-29
1.0.50	3 / 6	2025-06-29
1.0.49	3 / 6	2025-06-29
1.0.48	3 / 3	2025-06-29

v1.0.96

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.0.95

1 finding

LOW No provenance attestation provenance

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

v1.0.94

1 finding

LOW No provenance attestation provenance

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

v1.0.92

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.0.91

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.0.87

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.0.86

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.0.85

1 finding

LOW No provenance attestation provenance

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

v1.0.84

1 finding

LOW No provenance attestation provenance

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

v1.0.83

1 finding

LOW No provenance attestation provenance

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

v1.0.82

1 finding

LOW No provenance attestation provenance

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

v1.0.81

1 finding

LOW No provenance attestation provenance

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

v1.0.80

1 finding

LOW No provenance attestation provenance

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

v1.0.79

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.0.78

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.0.77

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.0.76

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.0.75

1 finding

LOW No provenance attestation provenance

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

v1.0.74

1 finding

LOW No provenance attestation provenance

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

v1.0.73

1 finding

LOW No provenance attestation provenance

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

v1.0.72

1 finding

LOW No provenance attestation provenance

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

v1.0.71

1 finding

LOW No provenance attestation provenance

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

v1.0.70

1 finding

LOW No provenance attestation provenance

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

v1.0.69

1 finding

LOW No provenance attestation provenance

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

v1.0.68

1 finding

LOW No provenance attestation provenance

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

v1.0.67

1 finding

LOW No provenance attestation provenance

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

v1.0.66

1 finding

LOW No provenance attestation provenance

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

v1.0.65

1 finding

LOW No provenance attestation provenance

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

v1.0.64

1 finding

LOW No provenance attestation provenance

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

v1.0.63

1 finding

LOW No provenance attestation provenance

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

v1.0.62

1 finding

LOW No provenance attestation provenance

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

v1.0.61

1 finding

LOW No provenance attestation provenance

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

v1.0.60

1 finding

LOW No provenance attestation provenance

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

v1.0.59

1 finding

LOW No provenance attestation provenance

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

v1.0.58

1 finding

LOW No provenance attestation provenance

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

v1.0.57

1 finding

LOW No provenance attestation provenance

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

v1.0.56

1 finding

LOW No provenance attestation provenance

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

v1.0.55

1 finding

LOW No provenance attestation provenance

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

v1.0.54

1 finding

LOW No provenance attestation provenance

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

v1.0.53

1 finding

LOW No provenance attestation provenance

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

v1.0.52

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.0.51

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.0.50

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.0.49

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.0.48

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.