@valbuild/core
Val - supercharged hard-coded content
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead is a minor metadata gap, not a supply-chain integrity failure. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package with 173 versions and 5 approved dependents; sparse README/keywords are a stable cosmetic trait. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @valbuild/core with 173 versions; name similarity to 'cors' is coincidental, not a squatting attempt. | ai |
Versions (showing 100 of 153)
| Version | Deps | Published |
|---|---|---|
| 0.97.1 | 1 / 1 | |
| 0.97.0 | 1 / 1 | |
| 0.96.3 | 1 / 1 | |
| 0.96.2 | 1 / 1 | |
| 0.96.0 | 1 / 1 | |
| 0.95.0 | 1 / 1 | |
| 0.94.0 | 1 / 1 | |
| 0.93.0 | 1 / 1 | |
| 0.92.0 | 1 / 1 | |
| 0.91.4 | 1 / 0 | |
| 0.91.3 | 1 / 0 | |
| 0.91.2 | 1 / 0 | |
| 0.91.1 | 1 / 0 | |
| 0.91.0 | 1 / 0 | |
| 0.90.0 | 1 / 0 | |
| 0.89.0 | 1 / 0 | |
| 0.88.0 | 1 / 0 | |
| 0.87.5 | 1 / 0 | |
| 0.87.4 | 1 / 0 | |
| 0.87.3 | 1 / 0 | |
| 0.87.2 | 1 / 0 | |
| 0.87.1 | 1 / 0 | |
| 0.87.0 | 1 / 0 | |
| 0.86.3 | 1 / 0 | |
| 0.86.2 | 1 / 0 | |
| 0.86.1 | 1 / 0 | |
| 0.86.0 | 1 / 0 | |
| 0.85.1 | 1 / 0 | |
| 0.85.0 | 1 / 0 | |
| 0.84.3 | 1 / 0 | |
| 0.84.2 | 1 / 0 | |
| 0.84.1 | 1 / 0 | |
| 0.84.0 | 1 / 0 | |
| 0.83.0 | 1 / 0 | |
| 0.82.0 | 1 / 0 | |
| 0.81.0 | 1 / 0 | |
| 0.80.0 | 1 / 0 | |
| 0.79.4 | 1 / 0 | |
| 0.79.3 | 1 / 0 | |
| 0.79.2 | 1 / 0 | |
| 0.79.1 | 1 / 0 | |
| 0.79.0 | 1 / 0 | |
| 0.78.3 | 1 / 0 | |
| 0.78.2 | 1 / 0 | |
| 0.78.1 | 1 / 0 | |
| 0.78.0 | 1 / 0 | |
| 0.77.1 | 1 / 0 | |
| 0.77.0 | 1 / 0 | |
| 0.76.1 | 1 / 0 | |
| 0.76.0 | 1 / 0 | |
| 0.75.5 | 1 / 0 | |
| 0.75.4 | 1 / 0 | |
| 0.75.3 | 1 / 0 | |
| 0.75.2 | 1 / 0 | |
| 0.75.1 | 1 / 0 | |
| 0.75.0 | 1 / 0 | |
| 0.74.0 | 1 / 0 | |
| 0.73.2 | 1 / 0 | |
| 0.73.1 | 1 / 0 | |
| 0.73.0 | 1 / 0 | |
| 0.72.4 | 1 / 0 | |
| 0.72.3 | 1 / 0 | |
| 0.72.2 | 1 / 0 | |
| 0.72.1 | 1 / 0 | |
| 0.72.0 | 1 / 0 | |
| 0.69.3 | 1 / 0 | |
| 0.69.1 | 1 / 0 | |
| 0.69.0 | 1 / 0 | |
| 0.68.0 | 1 / 0 | |
| 0.67.1 | 1 / 0 | |
| 0.67.0 | 1 / 0 | |
| 0.66.0 | 2 / 0 | |
| 0.65.3 | 2 / 0 | |
| 0.65.2 | 2 / 0 | |
| 0.65.0 | 2 / 0 | |
| 0.64.0 | 2 / 0 | |
| 0.63.6 | 2 / 0 | |
| 0.63.5 | 2 / 0 | |
| 0.63.1 | 2 / 0 | |
| 0.63.0 | 2 / 0 | |
| 0.62.6 | 1 / 0 | |
| 0.62.5 | 1 / 0 | |
| 0.62.4 | 1 / 0 | |
| 0.62.3 | 1 / 0 | |
| 0.62.2 | 1 / 0 | |
| 0.62.1 | 1 / 0 | |
| 0.62.0 | 1 / 0 | |
| 0.61.0 | 1 / 0 | |
| 0.60.27 | 1 / 0 | |
| 0.60.24 | 1 / 0 | |
| 0.60.23 | 1 / 0 | |
| 0.60.22 | 1 / 0 | |
| 0.60.21 | 1 / 0 | |
| 0.60.20 | 1 / 0 | |
| 0.60.19 | 1 / 0 | |
| 0.60.18 | 1 / 0 | |
| 0.60.17 | 1 / 0 | |
| 0.60.16 | 1 / 0 | |
| 0.60.15 | 1 / 0 | |
| 0.60.14 | 1 / 0 |
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.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.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.3
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.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.6
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.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.
v0.60.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.