@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 8 of 220)
| Version | Deps | Published |
|---|---|---|
| 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.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.