@farming-labs/docs
Modern, flexible MDX-based docs framework — core types, config, and CLI
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Declared dependency; used in build/config pipeline, not direct imports. | ai | |
| phantom-deps | phantom-dep:gray-matter | AI (phantom-deps): Declared dependency; used in build/config pipeline, not direct imports. | ai | |
| phantom-deps | phantom-dep:@clack/prompts | AI (phantom-deps): Declared dependency; used in build/config pipeline, not direct imports. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped docs framework; name similarity to 'cors' is coincidental, not a typosquat attempt. | ai |
Versions (showing 97 of 220)
| Version | Deps | Published |
|---|---|---|
| 0.1.38 | 6 / 4 | |
| 0.1.37 | 6 / 4 | |
| 0.1.36 | 6 / 4 | |
| 0.1.35 | 6 / 4 | |
| 0.1.34 | 6 / 4 | |
| 0.1.33 | 6 / 4 | |
| 0.1.32 | 6 / 4 | |
| 0.1.31 | 6 / 4 | |
| 0.1.30 | 6 / 4 | |
| 0.1.29 | 6 / 4 | |
| 0.1.28 | 6 / 4 | |
| 0.1.27 | 6 / 4 | |
| 0.1.25 | 6 / 4 | |
| 0.1.24 | 6 / 4 | |
| 0.1.23 | 6 / 4 | |
| 0.1.22 | 6 / 4 | |
| 0.1.21 | 6 / 4 | |
| 0.1.20 | 6 / 4 | |
| 0.1.19 | 6 / 4 | |
| 0.1.18 | 6 / 4 | |
| 0.1.17 | 6 / 4 | |
| 0.1.16 | 6 / 4 | |
| 0.1.13 | 6 / 4 | |
| 0.1.12 | 6 / 4 | |
| 0.1.11 | 6 / 4 | |
| 0.1.10 | 6 / 4 | |
| 0.1.9 | 6 / 4 | |
| 0.1.8 | 6 / 4 | |
| 0.1.7 | 6 / 4 | |
| 0.1.6 | 6 / 4 | |
| 0.1.5 | 6 / 4 | |
| 0.1.4 | 6 / 4 | |
| 0.1.3 | 6 / 4 | |
| 0.1.2 | 6 / 4 | |
| 0.1.1 | 6 / 4 | |
| 0.1.0 | 4 / 4 | |
| 0.0.72 | 4 / 4 | |
| 0.0.71 | 4 / 4 | |
| 0.0.68 | 4 / 4 | |
| 0.0.66 | 4 / 4 | |
| 0.0.65 | 4 / 4 | |
| 0.0.64 | 4 / 4 | |
| 0.0.63 | 4 / 4 | |
| 0.0.62 | 4 / 4 | |
| 0.0.61 | 4 / 4 | |
| 0.0.60 | 4 / 4 | |
| 0.0.59 | 4 / 4 | |
| 0.0.58 | 4 / 4 | |
| 0.0.57 | 4 / 4 | |
| 0.0.56 | 4 / 4 | |
| 0.0.55 | 4 / 4 | |
| 0.0.54 | 4 / 4 | |
| 0.0.53 | 4 / 4 | |
| 0.0.52 | 4 / 4 | |
| 0.0.51 | 4 / 4 | |
| 0.0.50 | 4 / 4 | |
| 0.0.48 | 4 / 4 | |
| 0.0.47 | 4 / 4 | |
| 0.0.46 | 4 / 4 | |
| 0.0.45 | 4 / 4 | |
| 0.0.44 | 4 / 4 | |
| 0.0.43 | 4 / 4 | |
| 0.0.38 | 3 / 4 | |
| 0.0.37 | 3 / 4 | |
| 0.0.36 | 3 / 4 | |
| 0.0.34 | 3 / 4 | |
| 0.0.33 | 3 / 4 | |
| 0.0.32 | 3 / 4 | |
| 0.0.31 | 3 / 4 | |
| 0.0.30 | 3 / 4 | |
| 0.0.29 | 3 / 4 | |
| 0.0.28 | 3 / 4 | |
| 0.0.27 | 3 / 4 | |
| 0.0.26 | 3 / 4 | |
| 0.0.25 | 3 / 4 | |
| 0.0.24 | 3 / 4 | |
| 0.0.23 | 3 / 4 | |
| 0.0.22 | 3 / 4 | |
| 0.0.21 | 3 / 4 | |
| 0.0.20 | 3 / 4 | |
| 0.0.19 | 3 / 4 | |
| 0.0.18 | 3 / 4 | |
| 0.0.17 | 3 / 4 | |
| 0.0.16 | 3 / 4 | |
| 0.0.15 | 3 / 4 | |
| 0.0.14 | 3 / 4 | |
| 0.0.12 | 3 / 4 | |
| 0.0.11 | 3 / 4 | |
| 0.0.10 | 3 / 4 | |
| 0.0.9 | 3 / 4 | |
| 0.0.8 | 3 / 4 | |
| 0.0.7 | 3 / 4 | |
| 0.0.6 | 3 / 4 | |
| 0.0.5 | 3 / 4 | |
| 0.0.4 | 3 / 3 | |
| 0.0.3 | 3 / 3 | |
| 0.0.2 | 3 / 3 |
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.