@cerbos/hub
Client library for interacting with Cerbos Hub from server-side Node.js applications
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 | encoded-string-file:lib/protobuf/cerbos/cloud/store/v1/store_pb.js | AI (source-diff): Base64 protobuf file descriptor passed to fileDesc(); standard @bufbuild/protobuf codegen pattern. | ai | |
| source-diff | encoded-string-file:src/protobuf/cerbos/cloud/apikey/v1/apikey_pb.ts | AI (source-diff): Base64-encoded protobuf file descriptor passed to fileDesc(); standard @bufbuild/protobuf pattern, not obfuscation. | ai | |
| source-diff | encoded-string-file:src/protobuf/cerbos/cloud/auth/v1/auth_pb.ts | AI (source-diff): Base64-encoded protobuf file descriptor; same benign @bufbuild/protobuf pattern. | ai | |
| source-diff | encoded-string-file:src/protobuf/cerbos/cloud/store/v1/store_pb.ts | AI (source-diff): Base64-encoded protobuf file descriptor; same benign @bufbuild/protobuf pattern. | ai | |
| source-diff | encoded-string-file:src/protobuf/buf/validate/validate_pb.ts | AI (source-diff): Base64-encoded protobuf file descriptor; same benign @bufbuild/protobuf pattern. | ai | |
| source-diff | encoded-string-file:lib/protobuf/cerbos/cloud/apikey/v1/apikey_pb.js | AI (source-diff): Base64 protobuf file descriptor generated by @bufbuild/protobuf toolchain; stable pattern across all versions of this package. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @cerbos/hub is a legitimate Cerbos SDK package; Levenshtein match to 'yup' is a false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.5.6 | 5 / 0 | |
| 0.5.5 | 5 / 0 | |
| 0.5.4 | 5 / 0 | |
| 0.5.3 | 5 / 0 | |
| 0.5.2 | 5 / 0 | |
| 0.5.1 | 6 / 1 | |
| 0.5.0 | 6 / 1 | |
| 0.4.0 | 6 / 1 | |
| 0.3.0 | 5 / 1 | |
| 0.2.4 | 5 / 1 | |
| 0.2.3 | 5 / 1 | |
| 0.2.2 | 5 / 1 | |
| 0.2.1 | 6 / 1 | |
| 0.2.0 | 6 / 1 | |
| 0.1.1 | 6 / 1 | |
| 0.1.0 | 6 / 1 |
v0.5.6
5 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.2
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
6 findingsAll previous maintainers (cerbosdev) were replaced by new maintainers (alexolivier, ahaines). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2025-10-14. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.