← Home

@tuwaio/docs-ui

npm Repository Homepage

Unified documentation package for the TUWA Ecosystem.

8
Versions
Apache-2.0
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

liastik

Keywords

reacttailwindcssui-kitutilstuwadocs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:clsx AI (phantom-deps): Direct dependency used in build/config; stable false positive. ai
phantom-deps phantom-dep:tailwind-merge AI (phantom-deps): Direct dependency used in build/config; stable false positive. ai
phantom-deps phantom-dep:@types/react-syntax-highlighter AI (phantom-deps): Framework-scoped type package; stable false positive. ai

Versions (showing 8 of 8)

Version Deps Published
0.0.9 5 / 15
0.0.8 5 / 15
0.0.7 5 / 15
0.0.6 5 / 15
0.0.5 5 / 15
0.0.4 5 / 15
0.0.3 5 / 15
0.0.2 6 / 10

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

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

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

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

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

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

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