@nuxt/content
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:nuxt-component-meta | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm packages have provenance; not a blocker for established packages. | ai | |
| phantom-deps | phantom-dep:@shikijs/langs | AI (phantom-deps): Nuxt module pattern; syntax highlighting langs referenced in config, not direct imports. | ai | |
| dependencies | unvetted-dep:@sqlite.org/sqlite-wasm | AI (dependencies): Official SQLite WASM package from sqlite.org; expected dependency for content module DB support. | ai | |
| phantom-deps | phantom-dep:mdast-util-to-hast | AI (phantom-deps): Nuxt module pattern; markdown processing dep referenced in build config. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Nuxt module pattern; used for live preview/dev features, referenced in config. | ai | |
| phantom-deps | phantom-dep:consola | AI (phantom-deps): Nuxt module pattern; deps referenced in build config rather than direct imports. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.14.0 | 47 / 29 | |
| 3.13.0 | 47 / 29 | |
| 3.12.0 | 47 / 29 | |
| 3.11.2 | 48 / 29 | |
| 3.11.1 | 48 / 29 | |
| 3.10.0 | 48 / 29 | |
| 3.9.0 | 48 / 29 | |
| 3.8.1 | 48 / 29 | |
| 3.6.1 | 45 / 26 | |
| 3.6.0 | 45 / 26 |
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.