@orval/core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): tinyglobby is a well-known glob library replacing globby; not a suspicious dependency addition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo subpackage; sparse metadata is expected and consistent across all 118 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern for this scoped monorepo package across all versions. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @orval/core is the core module of the orval codegen suite, not a typosquat of cors. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 8.15.0 | 11 / 9 | |
| 8.14.0 | 11 / 9 | |
| 8.13.0 | 11 / 9 | |
| 8.12.3 | 11 / 9 | |
| 8.12.1 | 11 / 9 | |
| 8.11.0 | 11 / 9 | |
| 8.10.0 | 11 / 9 | |
| 8.9.1 | 11 / 9 | |
| 8.9.0 | 11 / 9 | |
| 8.8.1 | 11 / 9 | |
| 8.8.0 | 11 / 9 | |
| 8.7.0 | 11 / 9 | |
| 8.6.1 | 11 / 9 | |
| 8.6.0 | 11 / 9 | |
| 8.5.3 | 10 / 9 | |
| 8.5.2 | 10 / 9 | |
| 8.5.1 | 10 / 9 | |
| 8.5.0 | 10 / 9 | |
| 8.4.2 | 11 / 9 | |
| 8.4.1 | 11 / 9 | |
| 8.4.0 | 11 / 9 | |
| 8.3.0 | 11 / 9 | |
| 8.2.0 | 11 / 9 | |
| 7.21.0 | 19 / 16 |
v8.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.3
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: melloware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.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: melloware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.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: melloware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.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: melloware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.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: melloware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
2 findingsPackage name '@orval/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.