@code0-tech/tucana
Code0 GRPC Protocol
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/shared.flow_pb-BNS2UoJj.cjs | AI (source-diff): Minified protobuf-ts generated CJS bundle; expected output for this gRPC protocol package. | ai | |
| source-diff | obfuscated-file:dist/shared.function_pb-B9l5kdQt.cjs | AI (source-diff): Minified protobuf-ts generated CJS bundle; expected output for this gRPC protocol package. | ai | |
| source-diff | obfuscated-file:dist/shared.runtime_usage_pb-CVahFg9u.cjs | AI (source-diff): Minified protobuf-ts generated CJS bundle; expected output for this gRPC protocol package. | ai | |
| source-diff | obfuscated-file:dist/shared.runtime_usage_pb-CSRup69H.cjs | AI (source-diff): Minified protobuf-ts generated output; consistent with build pipeline for this gRPC protocol package. | ai | |
| source-diff | obfuscated-file:dist/shared.flow_pb-DrDw61IF.cjs | AI (source-diff): Minified protobuf-ts generated output; consistent with build pipeline for this gRPC protocol package. | ai | |
| source-diff | obfuscated-file:dist/shared.function_pb-BErnwHWO.cjs | AI (source-diff): Minified protobuf-ts runtime (base64, wire types); standard build artifact for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tiny payload and empty index.js are expected for a generated-code stub package in a monorepo. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Established org package with 36 versions; 0.0.0 is a known bootstrap pattern for generated protobuf packages. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Package generates many protobuf files from .proto definitions; large file counts are expected for this gRPC protocol library. | ai | |
| source-diff | obfuscated-file:dist/shared.flow_pb-BBS51Wou.cjs | AI (source-diff): Minified vite build output of protobuf-ts generated code; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/shared.runtime_usage_pb-Cgr2Xle6.cjs | AI (source-diff): Minified vite build output of protobuf-ts runtime; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/shared.runtime_usage_pb-6pp995qK.cjs | AI (source-diff): Minified Vite/protobuf-ts runtime bundle; base64 and wire-type logic is standard protobuf-ts internals. | ai | |
| source-diff | obfuscated-file:dist/shared.flow_pb-CAu-uZAs.cjs | AI (source-diff): Minified Vite/protobuf-ts build output; content is recognizable protobuf binary codec, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/shared.runtime_usage_pb-D4aGN4uQ.cjs | AI (source-diff): Minified protobuf-ts runtime; base64/wire-type code is standard protobuf-ts library output. | ai | |
| source-diff | obfuscated-file:dist/shared.flow_pb-CWFj5vbi.cjs | AI (source-diff): Minified protobuf-ts generated output; consistent with vite build of GRPC protocol package. | ai | |
| source-diff | obfuscated-file:dist/shared.flow_pb-BwIQ0MZP.cjs | AI (source-diff): Minified protobuf-ts generated code; expected build artifact for this gRPC protocol package. | ai | |
| source-diff | obfuscated-file:dist/shared.runtime_usage_pb-CYG2eLDw.cjs | AI (source-diff): Minified protobuf-ts runtime; expected build artifact for this gRPC protocol package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.0.73 | 0 / 6 | |
| 0.0.72 | 0 / 6 | |
| 0.0.71 | 0 / 6 | |
| 0.0.70 | 0 / 6 | |
| 0.0.69 | 0 / 6 | |
| 0.0.68 | 0 / 6 | |
| 0.0.67 | 0 / 6 | |
| 0.0.66 | 0 / 6 | |
| 0.0.65 | 0 / 6 | |
| 0.0.64 | 0 / 4 | |
| 0.0.62 | 0 / 4 | |
| 0.0.61 | 0 / 2 | |
| 0.0.60 | 0 / 2 | |
| 0.0.59 | 0 / 2 | |
| 0.0.58 | 0 / 2 | |
| 0.0.57 | 0 / 2 | |
| 0.0.56 | 0 / 2 | |
| 0.0.55 | 0 / 2 | |
| 0.0.54 | 0 / 2 | |
| 0.0.53 | 0 / 2 | |
| 0.0.52 | 0 / 2 | |
| 0.0.51 | 0 / 2 | |
| 0.0.50 | 0 / 2 | |
| 0.0.49 | 0 / 2 | |
| 0.0.48 | 0 / 2 | |
| 0.0.47 | 0 / 2 | |
| 0.0.46 | 0 / 2 | |
| 0.0.45 | 0 / 2 | |
| 0.0.44 | 0 / 2 | |
| 0.0.43 | 0 / 2 | |
| 0.0.42 | 0 / 2 | |
| 0.0.41 | 0 / 2 | |
| 0.0.40 | 0 / 2 | |
| 0.0.39 | 0 / 2 | |
| 0.0.38 | 0 / 2 | |
| 0.0.37 | 0 / 2 | |
| 0.0.0 | 0 / 2 |
v0.0.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.72
4 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.71
4 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.69
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.68
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.67
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.65
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.