@ovhcloud/ods-recipes
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/ods-react69-CvBotv7Q.js | AI (source-diff): Vite/Rollup minified bundle output; code is readable React/classnames, not malicious obfuscation. Stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): OVHcloud ODS packages consistently publish without Sigstore provenance; stable false positive for this org. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 19.7.0 | 3 / 16 | |
| 19.6.1 | 3 / 16 | |
| 19.6.0 | 3 / 16 | |
| 19.5.0 | 3 / 16 | |
| 19.4.1 | 3 / 16 | |
| 19.4.0 | 3 / 16 |
v19.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.6.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.6.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.