@nuxt/schema
Nuxt types and default configuration
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/_chunks/libs/@unhead/vue.d.mts | AI (source-diff): Type declaration file; token matches, no actual network/exec code. | ai | |
| source-diff | obfuscated-file:dist/_chunks/libs/@unhead/vue.d.mts | AI (source-diff): Bundled .d.mts declaration file; long type lines, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/_chunks/libs/@babel/parser.d.mts | AI (source-diff): Long lines are TS type-union declarations in bundled .d.mts, not obfuscation. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Nuxt org moved to nuxtbot CI publishing; SLSA provenance confirms legitimate transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Official Nuxt package; README links and missing keywords are not spam indicators here. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nuxtbot is the Nuxt org's CI bot account; stable across future versions. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): jiti is used indirectly via config resolution at runtime; phantom-dep pattern is expected for this package type. | ai | |
| dependencies | unvetted-dep:jiti | AI (dependencies): jiti is a legitimate TypeScript/ESM runtime loader, a core dependency in the Nuxt/Vite ecosystem. No malicious signals; stable use across many Nuxt versions. | ai | |
| dependencies | unvetted-dep:postcss-import-resolver | AI (dependencies): postcss-import-resolver is a standard PostCSS utility with no malicious signals; its use in a schema package for CSS config resolution is expected. | ai | |
| phantom-deps | phantom-dep:c12 | AI (phantom-deps): c12 is a Nuxt config loader used indirectly at runtime; phantom-dep pattern is expected for schema/config packages. | ai | |
| phantom-deps | phantom-dep:scule | AI (phantom-deps): scule is a string utility used indirectly; phantom-dep pattern is expected for schema/config packages. | ai | |
| phantom-deps | phantom-dep:create-require | AI (phantom-deps): create-require is a CJS compatibility shim used indirectly; phantom-dep pattern is expected for this package. | ai | |
| dependencies | unvetted-dep:@nuxt/ui-templates | AI (dependencies): @nuxt/ui-templates is a first-party Nuxt package; unvetted status is a false positive for ecosystem packages. | ai | |
| dependencies | unvetted-dep:uncrypto | AI (dependencies): uncrypto is a UnJS ecosystem utility for cross-runtime crypto. Legitimate dependency maintained by the same Nuxt/UnJS team. | ai | |
| dependencies | unvetted-dep:compatx | AI (dependencies): compatx is a UnJS ecosystem utility, the same org as Nuxt. Legitimate dependency with stable usage across Nuxt versions. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from danielroe to GitHub Actions CI/CD with SLSA provenance is a standard, secure publishing practice for the Nuxt framework. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are known Nuxt core team; reflects shift to automated CI/CD publishing with provenance attestation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): pkg-types is a legitimate UnJS ecosystem package maintained by the same org as Nuxt; its addition to @nuxt/schema is expected and benign. | ai | |
| dependencies | unvetted-dep:defu | AI (dependencies): defu is a well-known UnJS utility maintained by the same Nuxt/UnJS team; standard dependency across the Nuxt ecosystem. | ai | |
| dependencies | unvetted-dep:pkg-types | AI (dependencies): pkg-types is a stable utility package widely used in the Nuxt ecosystem; unvetted status does not reflect actual risk. | ai |
Versions (showing 11 of 111)
| Version | Deps | Published |
|---|---|---|
| 3.3.2 | 13 / 8 | |
| 3.3.1 | 13 / 8 | |
| 3.3.0 | 13 / 8 | |
| 3.2.3 | 13 / 8 | |
| 3.2.2 | 13 / 8 | |
| 3.2.1 | 13 / 8 | |
| 3.2.0 | 13 / 7 | |
| 3.1.2 | 13 / 7 | |
| 3.1.1 | 13 / 7 | |
| 3.1.0 | 13 / 7 | |
| 3.0.0 | 12 / 7 |
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (danielroe) than the most recent previously approved version (pi0) on 2023-01-25, but danielroe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (danielroe) than the most recent previously approved version (pi0) on 2023-01-24, but danielroe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.