@open-tender/utils MIT 40 versions

@open-tender/utils

npm Repository Homepage

A library of utils for use with Open Tender applications that utilize our cloud-based Order API.

40

Versions

MIT

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

Maintainers

areyes-iacmjoshua-nordshady.abdelaziz.farahatluong-iacmnayabkhanbrettspiegel

Keywords

open-tenderreactreduxecommercerestaurants

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Publisher matches existing maintainer name, consistent with legitimate manual publish.	ai	2026/07/16
provenance	missing-githead	AI (provenance): Byproduct of same publisher transition, no malicious change in diff.	ai	2026/07/16
publish-pattern	new-deps-added	AI (publish-pattern): date-fns/date-fns-tz are established, widely-used date utilities fitting the package's purpose.	ai	2026/07/16
provenance	publisher-changed	AI (provenance): Long-tenured publisher with strong approval history; change predates this version.	ai	2026/07/16

Versions (showing 40 of 140)

Version	Deps	Published
0.4.69	2 / 21	2024-09-30
0.4.68	2 / 21	2024-09-23
0.4.67	2 / 21	2024-08-27
0.4.66	2 / 21	2024-08-06
0.4.65	2 / 21	2024-08-01
0.4.64	2 / 21	2024-07-31
0.4.63	2 / 21	2024-07-24
0.4.62	2 / 21	2024-07-24
0.4.61	2 / 21	2024-07-02
0.4.60	0 / 23	2024-07-02
0.4.59	0 / 21	2024-07-02
0.4.58	0 / 21	2024-07-02
0.4.57	2 / 21	2024-07-02
0.4.56	2 / 21	2024-06-28
0.4.55	2 / 21	2024-06-28
0.4.54	2 / 21	2024-06-28
0.4.53	2 / 21	2024-06-28
0.4.52	2 / 20	2024-06-21
0.4.51	2 / 20	2024-06-21
0.4.50	2 / 20	2024-06-21
0.4.49	2 / 20	2024-06-20
0.4.48	2 / 20	2024-06-20
0.4.47	2 / 20	2024-06-20
0.4.46	2 / 20	2024-06-20
0.4.45	2 / 20	2024-06-14
0.4.44	2 / 21	2024-06-14
0.4.43	2 / 21	2024-06-13
0.4.42	2 / 21	2024-06-13
0.4.41	2 / 21	2024-06-13
0.4.40	2 / 21	2024-06-11
0.4.39	2 / 21	2024-05-17
0.4.38	2 / 21	2024-05-17
0.4.37	2 / 21	2024-05-17
0.4.36	2 / 21	2024-05-17
0.4.35	2 / 21	2024-05-17
0.4.34	2 / 21	2024-05-16
0.4.33	2 / 21	2024-05-16
0.4.32	2 / 21	2024-05-16
0.4.31	2 / 20	2024-05-05
0.4.30	2 / 20	2024-04-30

v0.4.69

1 finding

LOW No provenance attestation provenance

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

v0.4.68

1 finding

LOW No provenance attestation provenance

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

v0.4.67

1 finding

LOW No provenance attestation provenance

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

v0.4.66

1 finding

LOW No provenance attestation provenance

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

v0.4.65

2 findings

HIGH Publisher changed: vaulis11 → nasser_md (on 2024-08-01) provenance

This version was published by a different npm account than previous versions on 2024-08-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.4.64

2 findings

HIGH Publisher changed: vaulis11 → shady.abdelaziz.farahat (on 2024-07-31) provenance

This version was published by a different npm account than previous versions on 2024-07-31. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.4.63

2 findings

HIGH Publisher changed: vaulis11 → nasser_md (on 2024-07-24) provenance

This version was published by a different npm account than previous versions on 2024-07-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.4.62

2 findings

HIGH Publisher changed: vaulis11 → jcharrington (on 2024-07-24) provenance

This version was published by a different npm account than previous versions on 2024-07-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.4.61

1 finding

LOW No provenance attestation provenance

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

v0.4.60

1 finding

LOW No provenance attestation provenance

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

v0.4.59

1 finding

LOW No provenance attestation provenance

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

v0.4.58

1 finding

LOW No provenance attestation provenance

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

v0.4.57

1 finding

LOW No provenance attestation provenance

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

v0.4.56

1 finding

LOW No provenance attestation provenance

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

v0.4.55

1 finding

LOW No provenance attestation provenance

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

v0.4.54

1 finding

LOW No provenance attestation provenance

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

v0.4.53

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: jcharrington → vaulis11 (on 2024-06-28, known maintainer) provenance

This version was published by a different npm account (vaulis11) than the most recent previously approved version (jcharrington) on 2024-06-28, but vaulis11 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.4.52

1 finding

LOW No provenance attestation provenance

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

v0.4.51

1 finding

LOW No provenance attestation provenance

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

v0.4.50

1 finding

LOW No provenance attestation provenance

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

v0.4.49

1 finding

LOW No provenance attestation provenance

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

v0.4.48

1 finding

LOW No provenance attestation provenance

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

v0.4.47

1 finding

LOW No provenance attestation provenance

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

v0.4.46

1 finding

LOW No provenance attestation provenance

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

v0.4.45

1 finding

LOW No provenance attestation provenance

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

v0.4.44

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: vaulis11 → jcharrington (on 2024-06-14, known maintainer) provenance

This version was published by a different npm account (jcharrington) than the most recent previously approved version (vaulis11) on 2024-06-14, but jcharrington 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.4.43

1 finding

LOW No provenance attestation provenance

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

v0.4.42

1 finding

LOW No provenance attestation provenance

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

v0.4.41

1 finding

LOW No provenance attestation provenance

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

v0.4.40

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: jcharrington → vaulis11 (on 2024-06-11, known maintainer) provenance

This version was published by a different npm account (vaulis11) than the most recent previously approved version (jcharrington) on 2024-06-11, but vaulis11 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.4.39

1 finding

LOW No provenance attestation provenance

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

v0.4.38

1 finding

LOW No provenance attestation provenance

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

v0.4.37

1 finding

LOW No provenance attestation provenance

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

v0.4.36

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: vaulis11 → jcharrington (on 2024-05-17, known maintainer) provenance

This version was published by a different npm account (jcharrington) than the most recent previously approved version (vaulis11) on 2024-05-17, but jcharrington 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.4.35

1 finding

LOW No provenance attestation provenance

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

v0.4.34

1 finding

LOW No provenance attestation provenance

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

v0.4.33

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: jcharrington → vaulis11 (on 2024-05-16, known maintainer) provenance

This version was published by a different npm account (vaulis11) than the most recent previously approved version (jcharrington) on 2024-05-16, but vaulis11 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.4.32

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: jcharrington → vaulis11 (on 2024-05-16, known maintainer) provenance

This version was published by a different npm account (vaulis11) than the most recent previously approved version (jcharrington) on 2024-05-16, but vaulis11 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.4.31

1 finding

LOW No provenance attestation provenance

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

v0.4.30

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.