← Home

@asteby/metacore-ui

Metacore UI kit — data-table, layout shell, command-menu, hooks y primitives shadcn reutilizables

13
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

asteby-hq

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@radix-ui/react-dialog AI (dependencies): @radix-ui/react-dialog is a core Radix UI primitive used across the React ecosystem. No security concerns. ai
dependencies unvetted-dep:input-otp AI (dependencies): input-otp is a well-known, widely-used OTP input component for React with no known security issues. Stable false positive for this package. ai
dependencies unvetted-dep:@radix-ui/react-avatar AI (dependencies): @radix-ui/react-avatar is a core Radix UI primitive used across the React ecosystem. No security concerns. ai
dependencies unvetted-dep:@radix-ui/react-dropdown-menu AI (dependencies): @radix-ui/react-dropdown-menu is a core Radix UI primitive used across the React ecosystem. No security concerns. ai
dependencies unvetted-dep:@radix-ui/react-select AI (dependencies): @radix-ui/react-select is a core Radix UI primitive used across the React ecosystem. No security concerns. ai
dependencies unvetted-dep:@radix-ui/react-tooltip AI (dependencies): @radix-ui/react-tooltip is a core Radix UI primitive used across the React ecosystem. No security concerns. ai
provenance no-provenance AI (provenance): Lack of provenance is common (~88% of packages); no other indicators of supply chain compromise for this package. ai

Versions (showing 13 of 13)

Version Deps Published
2.4.1 28 / 12
2.4.0 28 / 12
2.3.0 28 / 12
2.2.0 28 / 12
2.1.2 28 / 12
2.1.1 28 / 12
2.1.0 28 / 12
2.0.1 28 / 12
2.0.0 28 / 12
0.7.0 28 / 11
0.6.0 28 / 11
0.5.0 28 / 11
0.3.0 28 / 11

v2.4.1

1 finding
INFO No provenance attestation provenance

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

v2.4.0

1 finding
INFO No provenance attestation provenance

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

v2.3.0

1 finding
INFO No provenance attestation provenance

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

v2.2.0

1 finding
INFO No provenance attestation provenance

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

v2.1.2

1 finding
INFO No provenance attestation provenance

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

v2.1.1

1 finding
INFO No provenance attestation provenance

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

v2.1.0

1 finding
INFO No provenance attestation provenance

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

1 finding
INFO No provenance attestation provenance

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

v0.7.0

1 finding
INFO No provenance attestation provenance

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

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

v0.5.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.