@enso-ui/typesense MIT 13 versions

@enso-ui/typesense

npm Repository Homepage

Typesense integration settings page for Enso UI.

13

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

aocneanugandescvlad.chvraftx24manuela.mindroc

Keywords

typesensevue

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): New dep is a legitimate Font Awesome sibling package, consistent with existing FA deps in this package.	ai	2026/05/27
dependencies	unvetted-dep:@fortawesome/pro-duotone-svg-icons	AI (dependencies): Legitimate FontAwesome pro icon package, consistent with other @fortawesome deps already declared.	ai	2026/04/30
phantom-deps	phantom-dep:@enso-ui/forms	AI (phantom-deps): Same org scope; likely re-exported or used indirectly via component composition rather than direct import.	ai	2026/04/28
phantom-deps	phantom-dep:@fortawesome/vue-fontawesome	AI (phantom-deps): Referenced in config files per finding; not a true phantom dep for this UI component package.	ai	2026/04/28

Versions (showing 13 of 13)

Version	Deps	Published
2.3.4	4 / 3	2026-04-28
2.3.3	4 / 3	2026-04-28
2.3.2	3 / 3	2026-04-25
2.3.1	5 / 1	2026-04-12
2.0.8	4 / 9	2022-01-10
2.0.7	3 / 9	2022-01-07
2.0.6	3 / 9	2021-12-23
2.0.5	3 / 9	2021-11-17
2.0.4	3 / 9	2021-11-17
2.0.3	3 / 9	2021-11-17
2.0.2	3 / 9	2021-11-16
2.0.1	3 / 9	2021-11-16
2.0.0	3 / 9	2021-11-12

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

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: aocneanu → gandesc (on 2021-12-23, known maintainer) provenance

This version was published by a different npm account (gandesc) than the most recent previously approved version (aocneanu) on 2021-12-23, but gandesc 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.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

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