@bondsports/date-time No license 51 versions

@bondsports/date-time

npm

51

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

ido.naveh.bondsportstetrobondbarak_matityahunoam.benzeevmatthew-cafiero-bondalex-bondsportsorinavehbondjon.ericksonslavabarkalpaulhoovergittybondaniambond

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:i18n	AI (phantom-deps): Declared in dependencies; used indirectly via config and type imports.	ai	2026/05/23
phantom-deps	phantom-dep:node	AI (phantom-deps): Declared in dependencies; used indirectly in config and type references.	ai	2026/05/23
phantom-deps	phantom-dep:lodash.clonedeep	AI (phantom-deps): Declared in dependencies; used indirectly via type imports and config.	ai	2026/05/23

Versions (showing 51 of 51)

Version	Deps	Published
3.13.0	4 / 24	2026-03-09
2.4.59	3 / 24	2026-04-16
2.4.55	3 / 24	2026-03-10
2.4.54	3 / 24	2026-02-24
2.4.53	4 / 24	2025-12-23
2.4.52	4 / 24	2025-09-16
2.4.50	4 / 24	2025-07-01
2.4.49	4 / 24	2025-06-29
2.4.48	4 / 24	2025-05-18
2.4.47	4 / 24	2025-05-06
2.4.46	4 / 24	2025-04-21
2.4.45	4 / 24	2025-03-20
2.4.44	4 / 24	2025-02-12
2.4.43	4 / 24	2025-02-12
2.4.42	4 / 24	2025-01-30
2.4.41	4 / 24	2025-01-06
2.4.40	4 / 24	2025-01-06
2.4.39	4 / 24	2025-01-05
2.4.38	4 / 24	2025-01-05
2.4.37	4 / 24	2025-01-05
2.4.36	4 / 24	2025-01-03
2.4.35	4 / 24	2025-01-02
2.4.34	4 / 24	2025-01-01
2.4.33	4 / 24	2024-12-30
2.4.32	4 / 24	2024-12-27
2.4.31	4 / 24	2024-12-27
2.4.30	4 / 24	2024-12-27
2.4.29	4 / 24	2024-12-19
2.4.28	4 / 24	2024-12-19
2.4.27	3 / 23	2024-12-15
2.4.26	3 / 23	2024-12-15
2.4.25	3 / 23	2024-12-12
2.4.24	3 / 23	2024-12-08
2.4.23	3 / 23	2024-12-06
2.4.22	3 / 23	2024-11-28
2.4.21	3 / 23	2024-11-18
2.4.20	3 / 23	2024-11-17
2.4.19	3 / 23	2024-11-17
2.4.18	3 / 23	2024-11-05
2.4.17	3 / 23	2024-10-18
2.4.15	3 / 23	2024-10-13
2.4.13	3 / 23	2024-10-10
2.4.12	3 / 23	2024-09-25
2.4.11	3 / 23	2024-09-23
2.4.10	3 / 23	2024-09-08
2.4.9	3 / 23	2024-08-25
2.4.7	3 / 23	2024-08-25
2.4.5	3 / 23	2024-08-25
2.4.3	3 / 23	2024-08-25
2.1.3	3 / 22	2024-08-23
2.1.1	3 / 22	2024-08-23

v2.4.47

1 finding

LOW No provenance attestation provenance

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

v2.4.46

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: jbknickerbocker → noam.benzeev (on 2025-04-21, known maintainer) provenance

This version was published by a different npm account (noam.benzeev) than the most recent previously approved version (jbknickerbocker) on 2025-04-21, but noam.benzeev 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.

v2.4.45

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: jbknickerbocker → noam.benzeev (on 2025-03-20, known maintainer) provenance

This version was published by a different npm account (noam.benzeev) than the most recent previously approved version (jbknickerbocker) on 2025-03-20, but noam.benzeev 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.

v2.4.44

1 finding

LOW No provenance attestation provenance

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

v2.4.43

1 finding

LOW No provenance attestation provenance

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

v2.4.42

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.

v2.4.41

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.

v2.4.40

1 finding

LOW No provenance attestation provenance

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

v2.4.39

1 finding

LOW No provenance attestation provenance

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

v2.4.38

1 finding

LOW No provenance attestation provenance

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

v2.4.37

1 finding

LOW No provenance attestation provenance

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

v2.4.36

1 finding

LOW No provenance attestation provenance

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

v2.4.35

1 finding

LOW No provenance attestation provenance

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

v2.4.34

1 finding

LOW No provenance attestation provenance

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

v2.4.33

1 finding

LOW No provenance attestation provenance

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

v2.4.32

1 finding

LOW No provenance attestation provenance

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

v2.4.31

1 finding

LOW No provenance attestation provenance

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

v2.4.30

1 finding

LOW No provenance attestation provenance

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

v2.4.29

1 finding

LOW No provenance attestation provenance

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

v2.4.28

1 finding

LOW No provenance attestation provenance

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

v2.4.27

1 finding

LOW No provenance attestation provenance

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

v2.4.26

1 finding

LOW No provenance attestation provenance

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

v2.4.25

1 finding

LOW No provenance attestation provenance

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

v2.4.24

1 finding

LOW No provenance attestation provenance

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

v2.4.23

1 finding

LOW No provenance attestation provenance

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

v2.4.22

1 finding

LOW No provenance attestation provenance

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

v2.4.21

1 finding

LOW No provenance attestation provenance

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

v2.4.20

1 finding

LOW No provenance attestation provenance

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

v2.4.19

1 finding

LOW No provenance attestation provenance

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

v2.4.18

1 finding

LOW No provenance attestation provenance

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

v2.4.17

1 finding

LOW No provenance attestation provenance

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

v2.4.15

1 finding

LOW No provenance attestation provenance

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

v2.4.13

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: jbknickerbocker → barak_matityahu (on 2024-10-10, known maintainer) provenance

This version was published by a different npm account (barak_matityahu) than the most recent previously approved version (jbknickerbocker) on 2024-10-10, but barak_matityahu 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.

v2.4.12

1 finding

LOW No provenance attestation provenance

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

v2.4.11

1 finding

LOW No provenance attestation provenance

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

v2.4.10

1 finding

LOW No provenance attestation provenance

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

v2.4.9

1 finding

LOW No provenance attestation provenance

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

v2.4.7

1 finding

LOW No provenance attestation provenance

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

v2.4.5

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.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.