@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, 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:better-sqlite3 | AI (phantom-deps): Used via config-driven db driver loading, not direct import. | ai | |
| dependencies | unvetted-dep:parse-git-config | AI (dependencies): Common, benign git-config parsing utility used for module metadata. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Used via config/build tooling, not direct import; standard for TS packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): h3 is a well-known Nuxt-ecosystem HTTP library, not a suspicious addition. | ai | |
| 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:consola | AI (phantom-deps): Nuxt module pattern; deps referenced in build config rather than direct imports. | 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:@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 |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.15.2 | 48 / 36 | |
| 3.15.1 | 48 / 36 | |
| 3.15.0 | 48 / 36 | |
| 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.11.0 | 48 / 30 | |
| 3.10.0 | 48 / 29 | |
| 3.9.0 | 48 / 29 | |
| 3.8.2 | 48 / 29 | |
| 3.8.1 | 48 / 29 | |
| 3.8.0 | 48 / 29 | |
| 3.7.1 | 47 / 29 | |
| 3.7.0 | 47 / 29 | |
| 3.6.3 | 45 / 27 | |
| 3.6.2 | 45 / 27 | |
| 3.6.1 | 45 / 26 | |
| 3.6.0 | 45 / 26 | |
| 3.5.1 | 44 / 26 | |
| 3.5.0 | 44 / 26 | |
| 3.4.0 | 44 / 26 | |
| 3.3.0 | 45 / 26 | |
| 3.2.2 | 45 / 26 | |
| 3.2.1 | 45 / 26 | |
| 3.2.0 | 45 / 26 | |
| 3.1.1 | 45 / 26 | |
| 3.1.0 | 45 / 26 | |
| 3.0.1 | 44 / 25 | |
| 3.0.0 | 44 / 25 |
v3.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.