@evergis/react
В данном репозитории находятся специфичные (в отличии от `@evergis/uilib-gl`) для `Evergis Online`, но в целом переиспользуемые на других проектах, построенных на Evergis API, React-компоненты.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Long-established scoped org package; sparse metadata is a stable characteristic, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Same pattern — declared dep used transitively or in config, not a security concern. | ai | |
| phantom-deps | phantom-dep:punycode | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:wkt | AI (phantom-deps): Large UI library; deps referenced in config/type files but not directly imported is expected pattern. | ai | |
| phantom-deps | phantom-dep:mapbox-gl-draw | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:@svgdotjs/svg.js | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:styled-system | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai |
Versions (showing 100 of 151)
| Version | Deps | Published |
|---|---|---|
| 4.0.74 | 32 / 27 | |
| 4.0.73 | 32 / 27 | |
| 4.0.72 | 32 / 27 | |
| 4.0.69 | 32 / 27 | |
| 4.0.68 | 32 / 27 | |
| 4.0.67 | 32 / 27 | |
| 4.0.66 | 32 / 27 | |
| 4.0.65 | 32 / 27 | |
| 4.0.64 | 32 / 27 | |
| 4.0.63 | 32 / 27 | |
| 4.0.62 | 32 / 27 | |
| 4.0.61 | 32 / 27 | |
| 4.0.59 | 32 / 27 | |
| 4.0.58 | 32 / 27 | |
| 4.0.57 | 32 / 27 | |
| 4.0.56 | 32 / 27 | |
| 4.0.55 | 32 / 27 | |
| 4.0.54 | 32 / 27 | |
| 4.0.53 | 32 / 27 | |
| 4.0.52 | 32 / 27 | |
| 4.0.51 | 32 / 27 | |
| 4.0.50 | 32 / 27 | |
| 4.0.49 | 32 / 27 | |
| 4.0.48 | 32 / 27 | |
| 4.0.47 | 32 / 27 | |
| 4.0.46 | 32 / 27 | |
| 4.0.45 | 32 / 27 | |
| 4.0.44 | 32 / 27 | |
| 4.0.43 | 32 / 27 | |
| 4.0.42 | 32 / 27 | |
| 4.0.41 | 32 / 27 | |
| 4.0.40 | 32 / 27 | |
| 4.0.39 | 32 / 27 | |
| 4.0.38 | 32 / 27 | |
| 4.0.37 | 32 / 27 | |
| 4.0.36 | 32 / 27 | |
| 4.0.35 | 32 / 27 | |
| 4.0.34 | 32 / 27 | |
| 4.0.33 | 32 / 27 | |
| 4.0.32 | 32 / 27 | |
| 4.0.31 | 32 / 27 | |
| 4.0.30 | 32 / 27 | |
| 4.0.29 | 32 / 27 | |
| 4.0.28 | 32 / 27 | |
| 4.0.27 | 32 / 27 | |
| 4.0.26 | 32 / 27 | |
| 4.0.25 | 32 / 27 | |
| 4.0.24 | 32 / 27 | |
| 4.0.23 | 32 / 27 | |
| 4.0.22 | 32 / 27 | |
| 4.0.21 | 32 / 27 | |
| 4.0.20 | 32 / 27 | |
| 4.0.14 | 32 / 27 | |
| 4.0.13 | 32 / 27 | |
| 4.0.12 | 32 / 27 | |
| 4.0.11 | 32 / 27 | |
| 4.0.10 | 32 / 27 | |
| 4.0.9 | 32 / 27 | |
| 4.0.8 | 32 / 27 | |
| 4.0.7 | 32 / 27 | |
| 4.0.6 | 32 / 27 | |
| 4.0.5 | 32 / 27 | |
| 4.0.4 | 32 / 27 | |
| 4.0.3 | 32 / 27 | |
| 4.0.2 | 32 / 27 | |
| 4.0.1 | 32 / 27 | |
| 4.0.0 | 32 / 27 | |
| 3.1.133 | 32 / 27 | |
| 3.1.132 | 32 / 27 | |
| 3.1.131 | 32 / 27 | |
| 3.1.130 | 32 / 27 | |
| 3.1.129 | 32 / 27 | |
| 3.1.128 | 32 / 27 | |
| 3.1.127 | 32 / 27 | |
| 3.1.126 | 32 / 27 | |
| 3.1.125 | 32 / 27 | |
| 3.1.124 | 32 / 27 | |
| 3.1.123 | 32 / 27 | |
| 3.1.122 | 32 / 27 | |
| 3.1.121 | 32 / 27 | |
| 3.1.120 | 32 / 27 | |
| 3.1.119 | 32 / 27 | |
| 3.1.118 | 32 / 27 | |
| 3.1.117 | 32 / 27 | |
| 3.1.113 | 32 / 27 | |
| 3.1.112 | 32 / 27 | |
| 3.1.111 | 32 / 27 | |
| 3.1.110 | 32 / 27 | |
| 3.1.109 | 32 / 27 | |
| 3.1.108 | 32 / 27 | |
| 3.1.107 | 31 / 27 | |
| 3.1.106 | 31 / 27 | |
| 3.1.105 | 31 / 27 | |
| 3.1.104 | 31 / 27 | |
| 3.1.103 | 31 / 27 | |
| 3.1.102 | 30 / 27 | |
| 3.1.101 | 30 / 27 | |
| 3.1.100 | 30 / 27 | |
| 3.1.96 | 30 / 27 | |
| 3.1.95 | 30 / 27 |
v4.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.67
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-06-01, 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.
v4.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.62
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-05-21, 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.
v4.0.61
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-05-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.
v4.0.59
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-05-19, 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.
v4.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.57
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-05-15, 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.
v4.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.54
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-05-07, 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.
v4.0.53
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-05-06, 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.
v4.0.52
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-05-06, 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.
v4.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.44
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-04-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.
v4.0.43
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-04-27, 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.
v4.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.41
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-04-24, 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.
v4.0.40
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-04-23, 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.
v4.0.39
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-23, 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.
v4.0.38
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-23, 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.
v4.0.37
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-22, 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.
v4.0.36
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-22, 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.
v4.0.35
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-04-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.
v4.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.33
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-04-20, 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.
v4.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.31
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-15, 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.
v4.0.30
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-13, 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.
v4.0.29
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-10, 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.
v4.0.28
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-10, 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.
v4.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.25
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-04-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.
v4.0.24
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-04-08, 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.
v4.0.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-04-08, 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.
v4.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-03-28, 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.
v4.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-03-24, 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.
v4.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-03-24, 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.
v4.0.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v4.0.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-03-18, 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.
v4.0.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-03-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.
v4.0.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-03-15, 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.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-03-10, 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.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-03-06, 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.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-03-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.
v3.1.133
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-03-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.
v3.1.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.128
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-02-25, 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.
v3.1.127
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-02-25, 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.
v3.1.126
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-02-19, 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.
v3.1.125
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-02-16, 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.
v3.1.124
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-02-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.
v3.1.123
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-02-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.
v3.1.122
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-02-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.
v3.1.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.118
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-02-06, 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.
v3.1.117
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-02-04, 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.
v3.1.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.112
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v3.1.111
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-01-23, 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.
v3.1.110
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-01-22, 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.
v3.1.109
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2026-01-22, 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.
v3.1.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.107
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-01-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.
v3.1.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.104
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-01-13, 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.
v3.1.103
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (arfeo) than the most recent previously approved version (alexanderbom) on 2026-01-12, 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.
v3.1.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.101
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v3.1.100
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2025-12-24, 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.
v3.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.