@valbuild/next
Val NextJS: hard-coded content - super-charged
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA attestation present; missing gitHead is a metadata gap, not a security risk for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA/Sigstore attestation — legitimate CI/CD migration, not a compromise. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Scoped monorepo package; 2-edit distance to knex is coincidental. | ai | |
| dependencies | unvetted-dep:@valbuild/ui | AI (dependencies): Sibling @valbuild monorepo package at matching version; expected dependency. | ai | |
| dependencies | unvetted-dep:@valbuild/core | AI (dependencies): Sibling @valbuild monorepo package at matching version; expected dependency. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): @valbuild/next is a Next.js integration package in the @valbuild monorepo, not a nuxt typosquat. | ai | |
| dependencies | unvetted-dep:@valbuild/server | AI (dependencies): Sibling @valbuild monorepo package at matching version; expected dependency. | ai | |
| dependencies | unvetted-dep:@valbuild/shared | AI (dependencies): Sibling @valbuild monorepo package at matching version; expected dependency. | ai | |
| dependencies | unvetted-dep:@valbuild/react | AI (dependencies): Sibling @valbuild monorepo package at matching version; expected dependency. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped monorepo package; 2-edit distance to jest is coincidental. | ai |
Versions (showing 100 of 180)
| Version | Deps | Published |
|---|---|---|
| 0.97.2 | 7 / 8 | |
| 0.97.1 | 7 / 8 | |
| 0.97.0 | 7 / 8 | |
| 0.96.3 | 7 / 3 | |
| 0.96.2 | 7 / 3 | |
| 0.96.1 | 7 / 3 | |
| 0.96.0 | 7 / 3 | |
| 0.95.0 | 7 / 3 | |
| 0.94.0 | 7 / 3 | |
| 0.93.0 | 7 / 3 | |
| 0.92.1 | 7 / 3 | |
| 0.92.0 | 7 / 3 | |
| 0.91.4 | 7 / 1 | |
| 0.91.3 | 7 / 1 | |
| 0.91.2 | 7 / 1 | |
| 0.91.1 | 7 / 1 | |
| 0.91.0 | 7 / 1 | |
| 0.90.0 | 7 / 1 | |
| 0.89.0 | 7 / 1 | |
| 0.88.0 | 7 / 1 | |
| 0.87.5 | 7 / 1 | |
| 0.87.4 | 7 / 1 | |
| 0.87.3 | 7 / 1 | |
| 0.87.2 | 7 / 1 | |
| 0.87.1 | 7 / 1 | |
| 0.87.0 | 7 / 1 | |
| 0.86.3 | 7 / 1 | |
| 0.86.2 | 7 / 1 | |
| 0.86.1 | 7 / 1 | |
| 0.86.0 | 7 / 1 | |
| 0.85.1 | 7 / 1 | |
| 0.85.0 | 7 / 1 | |
| 0.84.3 | 7 / 1 | |
| 0.84.2 | 7 / 1 | |
| 0.84.1 | 7 / 1 | |
| 0.84.0 | 7 / 1 | |
| 0.83.0 | 7 / 1 | |
| 0.82.0 | 7 / 1 | |
| 0.81.0 | 7 / 1 | |
| 0.80.0 | 7 / 1 | |
| 0.79.4 | 7 / 1 | |
| 0.79.3 | 7 / 1 | |
| 0.79.2 | 7 / 1 | |
| 0.79.1 | 7 / 1 | |
| 0.79.0 | 7 / 1 | |
| 0.78.3 | 7 / 1 | |
| 0.78.2 | 7 / 1 | |
| 0.78.1 | 7 / 1 | |
| 0.78.0 | 7 / 1 | |
| 0.77.1 | 7 / 1 | |
| 0.77.0 | 7 / 1 | |
| 0.76.1 | 7 / 1 | |
| 0.76.0 | 7 / 1 | |
| 0.75.5 | 7 / 1 | |
| 0.75.4 | 7 / 1 | |
| 0.75.3 | 7 / 1 | |
| 0.75.2 | 7 / 1 | |
| 0.75.1 | 7 / 1 | |
| 0.75.0 | 7 / 1 | |
| 0.74.0 | 7 / 1 | |
| 0.73.2 | 7 / 1 | |
| 0.73.1 | 7 / 1 | |
| 0.73.0 | 7 / 1 | |
| 0.72.4 | 7 / 1 | |
| 0.72.3 | 7 / 1 | |
| 0.72.2 | 7 / 1 | |
| 0.72.1 | 7 / 1 | |
| 0.72.0 | 7 / 1 | |
| 0.69.3 | 7 / 1 | |
| 0.69.2 | 7 / 1 | |
| 0.69.1 | 7 / 1 | |
| 0.69.0 | 7 / 1 | |
| 0.68.2 | 7 / 1 | |
| 0.68.1 | 7 / 1 | |
| 0.68.0 | 7 / 1 | |
| 0.67.1 | 7 / 1 | |
| 0.67.0 | 7 / 1 | |
| 0.66.0 | 7 / 1 | |
| 0.65.2 | 7 / 1 | |
| 0.65.1 | 7 / 1 | |
| 0.65.0 | 7 / 1 | |
| 0.64.0 | 7 / 1 | |
| 0.63.5 | 6 / 1 | |
| 0.63.3 | 6 / 1 | |
| 0.63.1 | 6 / 1 | |
| 0.63.0 | 6 / 1 | |
| 0.62.6 | 6 / 1 | |
| 0.62.5 | 6 / 1 | |
| 0.62.4 | 6 / 1 | |
| 0.62.3 | 6 / 1 | |
| 0.62.2 | 6 / 1 | |
| 0.62.1 | 6 / 1 | |
| 0.62.0 | 6 / 1 | |
| 0.61.0 | 6 / 1 | |
| 0.60.27 | 6 / 1 | |
| 0.60.24 | 6 / 1 | |
| 0.60.23 | 6 / 1 | |
| 0.60.22 | 6 / 1 | |
| 0.60.21 | 6 / 1 | |
| 0.60.20 | 6 / 1 |
v0.75.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.75.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.75.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.75.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.75.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.73.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.72.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.72.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.72.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.68.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.68.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.67.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.