@sentio/protos
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:nice-grpc | AI (phantom-deps): nice-grpc is a declared runtime dependency for gRPC bindings; not a phantom dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Generated protobuf package; missing metadata is normal for internal/build artifacts. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adds official @bufbuild/protobuf, required peer for generated code. | ai | |
| source-diff | obfuscated-file:dist/service/common/protos/common_pb.js | AI (source-diff): protoc-gen-es generated descriptor with base64 blob, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/processor/protos/processor_pb.js | AI (source-diff): protoc-gen-es generated descriptor with base64 blob, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/service/common/protos/common_pb.js | AI (source-diff): protoc-gen-es generated file with base64 proto descriptor, not obfuscation | ai | |
| source-diff | obfuscated-file:lib/processor/protos/processor_pb.js | AI (source-diff): protoc-gen-es generated file with base64 proto descriptor, not obfuscation | ai | |
| source-diff | obfuscated-file:src/service/common/protos/common_pb.ts | AI (source-diff): protoc-gen-es generated file with base64 proto descriptor, not obfuscation | ai | |
| source-diff | obfuscated-file:src/processor/protos/processor_pb.ts | AI (source-diff): protoc-gen-es generated file with base64 proto descriptor, not obfuscation | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 4.3.4 | 1 / 0 | |
| 4.3.3 | 1 / 0 | |
| 4.3.2 | 1 / 0 | |
| 4.3.1 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.2 | 1 / 0 | |
| 4.2.1 | 1 / 0 | |
| 4.2.0 | 1 / 0 | |
| 4.1.0 | 1 / 0 | |
| 4.0.0 | 1 / 0 | |
| 3.8.1 | 4 / 0 | |
| 3.8.0 | 4 / 0 | |
| 3.7.0 | 4 / 0 | |
| 3.6.2 | 4 / 0 | |
| 3.6.0 | 4 / 0 | |
| 3.5.0 | 4 / 0 | |
| 3.4.2 | 4 / 0 | |
| 3.4.0 | 4 / 0 | |
| 3.2.0 | 4 / 0 | |
| 3.0.1 | 4 / 0 | |
| 2.63.1 | 4 / 0 | |
| 2.63.0 | 4 / 0 | |
| 2.62.7 | 4 / 0 | |
| 2.62.6 | 4 / 0 |
v4.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.