← Home

@hedystia/view

npm Repository Homepage

Reactive UI engine — fine-grained signals, no Virtual DOM, real DOM nodes

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

Maintainers

zastinian

Keywords

hedystiaviewuireactivesignalstypescripttype-safejsx

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:vite AI (typosquat): Scoped UI library with vite as an optional peer dep; name similarity is intentional, not squatting. ai

Versions (showing 24 of 24)

Version Deps Published
2.3.9 0 / 2
2.3.8 0 / 2
2.3.7 0 / 2
2.3.6 0 / 2
2.3.5 0 / 2
2.3.4 0 / 2
2.3.3 0 / 2
2.3.2 0 / 2
2.3.1 0 / 2
2.2.13 0 / 2
2.2.12 0 / 2
2.2.11 0 / 2
2.2.9 0 / 2
2.2.8 0 / 2
2.2.7 0 / 2
2.2.6 0 / 2
2.2.5 0 / 2
2.2.4 0 / 2
2.2.3 0 / 2
2.2.2 0 / 2
2.2.1 0 / 2
2.2.0 0 / 2
2.1.1 0 / 1
2.1.0 0 / 0

v2.3.9

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

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

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

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

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

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

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