@voicenter-team/nuxt-llms-generator
Nuxt 3 module for automatically generating AI-optimized documentation files (llms.txt, llms-full.txt, and individual .md files) from Umbraco CMS data using Anthropic's Claude API.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:i | AI (dependencies): Package `i` is a small, well-known i18n/inflection utility; no malicious history. | ai | |
| provenance | no-provenance | AI (provenance): Org-published Nuxt module; lack of provenance is common and no other risk signals present. | ai | |
| phantom-deps | phantom-dep:i | AI (phantom-deps): Config-only reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:npm | AI (phantom-deps): npm listed as dep for programmatic use in module build scripts; not a real phantom. | ai | |
| phantom-deps | phantom-dep:@voicenter-team/eslint-config-ts | AI (phantom-deps): Same-org eslint config; referenced in config files, not a runtime import concern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.13 | 11 / 14 | |
| 0.1.12 | 11 / 14 | |
| 0.1.11 | 10 / 14 | |
| 0.1.10 | 10 / 14 | |
| 0.1.3 | 9 / 14 | |
| 0.1.0 | 6 / 14 |
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.