← Home

@timeui/core

npm

Shared hooks, context providers (ConfigProvider, ThemeProvider) for TimeUI.

7
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

timeui

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Part of a coherent @timeui/* design-system monorepo; sparse metadata is common for early-stage org packages. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @timeui/core is a scoped UI library package; the levenshtein match to 'cors' is coincidental and not a typosquat. ai
phantom-deps phantom-dep:@timeui/utils AI (phantom-deps): Same-org sibling in a monorepo; may be re-exported or used indirectly without direct import. ai
phantom-deps phantom-dep:@timeui/tokens AI (phantom-deps): Same-org sibling in a monorepo; consistent with design-token re-export pattern. ai

Versions (showing 7 of 7)

Version Deps Published
1.5.4 3 / 11
1.5.3 3 / 11
1.5.2 3 / 11
1.5.1 3 / 11
1.5.0 3 / 11
1.1.0 3 / 11
1.0.0 3 / 11

v1.5.4

1 finding
LOW No provenance attestation provenance

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

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@timeui/core' is 1 edit(s) away from popular package 'cors'.

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.

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

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