← Home

@nuxt/ui-templates

npm Repository Homepage
20
Versions
—
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

nuxtbotantfuatinuxpi0clarkdodanielroe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): danielroe is a core Nuxt maintainer with a strong track record; infrequent releases of a stable UI templates package are expected, not indicative of account takeover. ai
provenance publisher-changed AI (provenance): antfu is a well-known Nuxt core team member; the pi0→antfu transition is a legitimate, documented maintainer handoff within the Nuxt ecosystem. ai
license uncommon-license:CC-BY-ND-4.0 AI (license): CC-BY-ND-4.0 is intentional for @nuxt/ui-templates, which distributes UI design templates rather than general-purpose code. This is stable for this package. ai

Versions (showing 20 of 20)

Version Deps Published
1.3.4 0 / 15
1.3.3 0 / 15
1.3.2 0 / 15
1.3.1 0 / 15
1.3.0 0 / 15
1.2.1 0 / 15
1.2.0 0 / 15
1.1.1 0 / 15
1.1.0 0 / 15
1.0.0 0 / 15
0.4.0 0 / 14
0.3.3 0 / 14
0.3.2 0 / 14
0.3.1 0 / 14
0.3.0 0 / 14
0.2.2 0 / 14
0.2.1 0 / 14
0.2.0 0 / 14
0.1.1 0 / 14
0.1.0 0 / 14

v1.3.4

1 finding
LOW No provenance attestation provenance

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

v1.3.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: danielroe.

LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: antfu → danielroe (on 2023-06-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-20. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH Publisher changed: pi0 → antfu (on 2023-01-06) provenance

This version was published by a different npm account than previous versions on 2023-01-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: atinux → pi0 (on 2022-07-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-21. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: pi0 → atinux (on 2022-07-12) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-12. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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