@farming-labs/nuxt-theme
Nuxt/Vue UI components for @farming-labs/docs — layout, sidebar, TOC, search, and theme toggle
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:sugar-high | AI (dependencies): sugar-high is a well-known lightweight syntax highlighter; not a risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm); no other risk signals present. | ai |
Versions (showing 51 of 266)
| Version | Deps | Published |
|---|---|---|
| 0.2.74 | 2 / 0 | |
| 0.2.73 | 2 / 0 | |
| 0.2.72 | 2 / 0 | |
| 0.2.71 | 2 / 0 | |
| 0.2.70 | 2 / 0 | |
| 0.2.69 | 2 / 0 | |
| 0.2.68 | 2 / 0 | |
| 0.2.67 | 2 / 0 | |
| 0.2.66 | 2 / 0 | |
| 0.2.65 | 2 / 0 | |
| 0.2.64 | 2 / 0 | |
| 0.2.63 | 2 / 0 | |
| 0.2.62 | 2 / 0 | |
| 0.2.61 | 2 / 0 | |
| 0.2.60 | 2 / 0 | |
| 0.2.59 | 2 / 0 | |
| 0.2.58 | 2 / 0 | |
| 0.2.57 | 2 / 0 | |
| 0.2.56 | 2 / 0 | |
| 0.2.55 | 2 / 0 | |
| 0.2.54 | 2 / 0 | |
| 0.2.53 | 2 / 0 | |
| 0.2.52 | 2 / 0 | |
| 0.2.50 | 2 / 0 | |
| 0.2.49 | 2 / 0 | |
| 0.2.48 | 2 / 0 | |
| 0.2.47 | 2 / 0 | |
| 0.2.46 | 2 / 0 | |
| 0.2.45 | 2 / 0 | |
| 0.2.44 | 2 / 0 | |
| 0.2.43 | 2 / 0 | |
| 0.2.42 | 2 / 0 | |
| 0.2.41 | 2 / 0 | |
| 0.2.40 | 2 / 0 | |
| 0.2.39 | 2 / 0 | |
| 0.2.38 | 2 / 0 | |
| 0.2.37 | 2 / 0 | |
| 0.2.36 | 2 / 0 | |
| 0.2.35 | 2 / 0 | |
| 0.2.34 | 2 / 0 | |
| 0.2.33 | 2 / 0 | |
| 0.2.32 | 2 / 0 | |
| 0.2.31 | 2 / 0 | |
| 0.2.30 | 2 / 0 | |
| 0.2.29 | 2 / 0 | |
| 0.2.28 | 2 / 0 | |
| 0.2.27 | 2 / 0 | |
| 0.2.26 | 2 / 0 | |
| 0.2.25 | 2 / 0 | |
| 0.2.24 | 2 / 0 | |
| 0.2.23 | 2 / 0 |
v0.2.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.