← Home

@evergis/uilib-gl

npm Repository

🏆 **Before start:**

66
Versions
MIT
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

eldarmamedovmaximgritsenkoarfeoart5255alexanderbom

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:imask AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:bowser AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:scroll AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:date-fns AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:find-and AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:platform AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:polished AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:cleave.js AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:deepmerge AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:lodash-es AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:react-imask AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:react-window AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:@tippyjs/react AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:vanilla-picker AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai
phantom-deps phantom-dep:regenerator-runtime AI (phantom-deps): Known implicit runtime dependency; stable for this package. ai
phantom-deps phantom-dep:autosuggest-highlight AI (phantom-deps): Declared dependency; heuristic false positive for this package. ai

Versions (showing 66 of 66)

Version Deps Published
1.0.121 24 / 57
1.0.120 24 / 57
1.0.119 24 / 57
1.0.118 24 / 57
1.0.117 24 / 57
1.0.116 24 / 57
1.0.115 24 / 57
1.0.114 24 / 57
1.0.113 24 / 57
1.0.112 24 / 52
1.0.111 24 / 52
1.0.109 24 / 52
1.0.108 24 / 52
1.0.107 24 / 52
1.0.106 24 / 52
1.0.105 24 / 52
1.0.104 24 / 52
1.0.103 24 / 52
1.0.102 24 / 52
1.0.101 24 / 52
1.0.100 24 / 52
1.0.99 24 / 52
1.0.98 24 / 52
1.0.97 24 / 52
1.0.96 24 / 52
1.0.95 24 / 52
1.0.94 24 / 52
1.0.93 24 / 52
1.0.92 24 / 52
1.0.91 24 / 52
1.0.90 24 / 52
1.0.89 24 / 52
1.0.88 24 / 52
1.0.87 24 / 52
1.0.86 24 / 52
1.0.85 24 / 52
1.0.84 24 / 52
1.0.83 24 / 52
1.0.82 24 / 52
1.0.81 24 / 52
1.0.80 24 / 52
1.0.79 24 / 52
1.0.78 24 / 52
1.0.77 24 / 52
1.0.76 24 / 52
1.0.75 24 / 52
1.0.74 24 / 52
1.0.73 24 / 52
1.0.72 24 / 52
1.0.71 24 / 52
1.0.70 24 / 52
1.0.69 24 / 52
1.0.68 24 / 52
1.0.67 24 / 52
1.0.66 24 / 52
1.0.64 24 / 52
1.0.63 24 / 52
1.0.62 24 / 52
1.0.61 24 / 52
1.0.60 24 / 52
1.0.59 24 / 52
1.0.58 24 / 52
1.0.57 24 / 52
1.0.56 24 / 52
1.0.1 21 / 40
1.0.0 21 / 40

v1.0.121

1 finding
LOW No provenance attestation provenance

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

v1.0.120

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: alexanderbom → arfeo (on 2026-07-16, known maintainer) provenance

This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-07-16, but arfeo 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.

v1.0.119

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: arfeo → alexanderbom (on 2026-07-09, known maintainer) provenance

This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-07-09, but alexanderbom 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.

v1.0.118

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: alexanderbom → arfeo (on 2026-07-02, known maintainer) provenance

This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-07-02, but arfeo 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.

v1.0.90

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: alexanderbom → arfeo (on 2026-03-25, known maintainer) provenance

This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-03-25, but arfeo 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.

v1.0.89

1 finding
LOW No provenance attestation provenance

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

v1.0.88

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: arfeo → alexanderbom (on 2026-03-20, known maintainer) provenance

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

v1.0.87

1 finding
LOW No provenance attestation provenance

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

v1.0.86

1 finding
LOW No provenance attestation provenance

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

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

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: alexanderbom → arfeo (on 2026-02-03, known maintainer) provenance

This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-02-03, but arfeo 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.

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

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: alexanderbom → arfeo (on 2026-01-28, known maintainer) provenance

This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-01-28, but arfeo 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.

v1.0.78

1 finding
LOW No provenance attestation provenance

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

v1.0.77

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: alexanderbom → arfeo (on 2026-01-21, known maintainer) provenance

This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-01-21, but arfeo 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.

v1.0.76

1 finding
LOW No provenance attestation provenance

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

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

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: arfeo → alexanderbom (on 2025-12-26, known maintainer) provenance

This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2025-12-26, but alexanderbom 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.

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

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: alexanderbom → arfeo (on 2025-12-19, known maintainer) provenance

This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2025-12-19, but arfeo 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.

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

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: arfeo → alexanderbom (on 2025-11-08, known maintainer) provenance

This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2025-11-08, but alexanderbom 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.

v1.0.60

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: arfeo → alexanderbom (on 2025-11-08, known maintainer) provenance

This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2025-11-08, but alexanderbom 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.

v1.0.59

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: alexanderbom → arfeo (on 2025-11-05, known maintainer) provenance

This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2025-11-05, but arfeo 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.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.56

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

v1.0.0

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.