@cerefox/codefactory-native-darwin-x64
Cerefox Code Factory pinned native libs (libsqlite3 + sqlite-vec) for darwin-x64
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Package's sole purpose is distributing libsqlite3 and sqlite-vec native dylibs; binaries are expected and covered by SLSA provenance. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.24.5 | 0 / 0 | |
| 0.24.4 | 0 / 0 | |
| 0.24.3 | 0 / 0 | |
| 0.24.2 | 0 / 0 | |
| 0.24.1 | 0 / 0 | |
| 0.24.0 | 0 / 0 | |
| 0.23.1 | 0 / 0 | |
| 0.23.0 | 0 / 0 | |
| 0.22.2 | 0 / 0 | |
| 0.22.1 | 0 / 0 | |
| 0.22.0 | 0 / 0 | |
| 0.21.0 | 0 / 0 | |
| 0.20.0 | 0 / 0 | |
| 0.19.0 | 0 / 0 | |
| 0.18.0 | 0 / 0 | |
| 0.17.0 | 0 / 0 | |
| 0.16.4 | 0 / 0 | |
| 0.16.2 | 0 / 0 |
v0.24.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.4
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.3
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.2
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.1
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.1
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.2
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.1
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.4
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.2
2 findingsPackage contains compiled binaries that could be backdoors: • libsqlite3.dylib • sqlite-vec.dylib
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.