@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, 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/types-CdKu8KmO.d.mts | AI (source-diff): Bundled .d.mts type declarations, minified formatting only. | ai | |
| source-diff | obfuscated-file:dist/agent-BMxMpEa0.mjs | AI (source-diff): Bundled build output with readable source comments; not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types-BVgucdVm.d.mts | AI (source-diff): Bundled .d.mts type declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-CtF_65E4.d.mts | AI (source-diff): Long-line trigger is a minified .d.mts type file, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-DKCNILor.d.mts | AI (source-diff): Bundled .d.mts type declarations, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/agent-B6szuz_8.mjs | AI (source-diff): Bundled build output (tsdown/rollup), readable region-commented source, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types-C5yQrqXc.d.mts | AI (source-diff): Sample shows readable typed declarations; long lines are minifier output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types-5-f3AZ9z.d.mts | AI (source-diff): Type declaration file with long doc-comment lines, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-R-DN23yw.d.mts | AI (source-diff): Bundled type declarations, readable JSDoc, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/agent-DXkXi-pS.mjs | AI (source-diff): Bundled tsdown output with readable source comments, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Normal growth of a docs framework's bundled dist output. | ai | |
| source-diff | obfuscated-file:dist/types-XqGLsmOD.d.mts | AI (source-diff): Bundled .d.mts type declarations, readable, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/agent-CaOBIVFy.mjs | AI (source-diff): Bundled tsdown output with readable source, not true obfuscation. | ai | |
| source-diff | bulk-obfuscated-files:dist | AI (source-diff): Bundled tsdown build output, sample shows legitimate MDX docs code, not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @mdx-js/mdx is an official, well-known dep aligned with package's MDX docs purpose. | ai | |
| phantom-deps | phantom-dep:picocolors | 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 | |
| phantom-deps | phantom-dep:gray-matter | 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 51 of 252)
| Version | Deps | Published |
|---|---|---|
| 0.2.57 | 9 / 6 | |
| 0.2.56 | 9 / 6 | |
| 0.2.55 | 8 / 6 | |
| 0.2.54 | 8 / 6 | |
| 0.2.53 | 8 / 6 | |
| 0.2.52 | 8 / 6 | |
| 0.2.50 | 8 / 6 | |
| 0.2.49 | 8 / 6 | |
| 0.2.48 | 8 / 6 | |
| 0.2.47 | 8 / 6 | |
| 0.2.46 | 8 / 6 | |
| 0.2.45 | 8 / 6 | |
| 0.2.44 | 8 / 6 | |
| 0.2.43 | 8 / 6 | |
| 0.2.42 | 8 / 6 | |
| 0.2.41 | 8 / 4 | |
| 0.2.40 | 8 / 4 | |
| 0.2.39 | 8 / 4 | |
| 0.2.38 | 8 / 4 | |
| 0.2.37 | 8 / 4 | |
| 0.2.36 | 8 / 4 | |
| 0.2.35 | 8 / 4 | |
| 0.2.34 | 8 / 4 | |
| 0.2.33 | 8 / 4 | |
| 0.2.32 | 8 / 4 | |
| 0.2.31 | 8 / 4 | |
| 0.2.30 | 8 / 4 | |
| 0.2.29 | 8 / 4 | |
| 0.2.28 | 8 / 4 | |
| 0.2.27 | 8 / 4 | |
| 0.2.26 | 8 / 4 | |
| 0.2.25 | 8 / 4 | |
| 0.2.24 | 8 / 4 | |
| 0.2.23 | 8 / 4 | |
| 0.2.22 | 8 / 4 | |
| 0.2.21 | 8 / 4 | |
| 0.2.19 | 8 / 4 | |
| 0.2.18 | 8 / 4 | |
| 0.2.17 | 8 / 4 | |
| 0.2.16 | 8 / 4 | |
| 0.2.15 | 8 / 4 | |
| 0.2.14 | 8 / 4 | |
| 0.2.13 | 8 / 4 | |
| 0.2.11 | 8 / 4 | |
| 0.2.10 | 8 / 4 | |
| 0.2.9 | 8 / 4 | |
| 0.2.8 | 8 / 4 | |
| 0.2.7 | 8 / 4 | |
| 0.2.6 | 8 / 4 | |
| 0.2.5 | 8 / 4 | |
| 0.2.4 | 8 / 4 |
v0.2.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.55
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.54
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.53
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.52
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.50
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.49
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.48
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.47
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.46
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.45
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.44
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.43
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.42
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.