← Home

@enso-ui/typesense

Typesense integration settings page for Enso UI.

4
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

aocneanugandescvlad.chvraftx24manuela.mindroc

Keywords

typesensevue

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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
dependencies unvetted-dep:@fortawesome/pro-duotone-svg-icons AI (dependencies): Legitimate FontAwesome pro icon package, consistent with other @fortawesome deps already declared. ai
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
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

Versions (showing 4 of 4)

Version Deps Published
2.3.4 4 / 3
2.3.3 4 / 3
2.3.2 3 / 3
2.3.1 5 / 1

v2.3.4

1 finding
LOW No provenance attestation provenance

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

v2.3.2

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