odiff-bin
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase from added binary architectures, not code injection. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall selects the correct platform binary from bundled raw_binaries/; stable pattern for this native-binary wrapper. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled binaries are the core product (platform-specific odiff executables); expected and documented for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used to invoke the selected platform binary — core functionality of this CLI wrapper. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.5.0 | 0 / 0 | |
| 4.4.4 | 0 / 0 | |
| 4.4.2 | 0 / 0 | |
| 4.4.1 | 0 / 0 | |
| 4.4.0 | 0 / 0 | |
| 4.3.8 | 0 / 0 | |
| 4.3.5 | 0 / 0 | |
| 4.3.0 | 0 / 0 | |
| 4.1.2 | 0 / 0 | |
| 4.0.1 | 0 / 0 |
v4.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.