@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 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.96.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.96.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.96.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.96.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.94.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.93.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.92.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.92.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.91.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.91.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.91.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.91.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.91.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.90.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.89.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.88.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.87.5
2 findingsThis version was published by a different npm account than previous versions on 2025-12-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.87.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.87.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.87.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.86.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.86.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.86.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.