Default package

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

enum CheckType

checks.proto:5

Used in: Filter, Violation

enum Ecosystem

models.proto:9

Used in: Package, PackageManifest, PackageManifestReport

message Exception

exceptions_spec.proto:5

Used in: ExceptionSuite

message ExceptionSuite

exceptions_spec.proto:14

message Filter

filter_suite_spec.proto:7

Used in: FilterSuite, Violation

message FilterInput

filter_input_spec.proto:23

message FilterInputPackageVersion

filter_input_spec.proto:17

Used in: FilterInput

message FilterInputVulnerabilities

filter_input_spec.proto:9

Only hold vulnerability IDs

Used in: FilterInput

message FilterSuite

filter_suite_spec.proto:17

message InsightLicenseInfo

insights_models.proto:33

Used in: PackageReport

message InsightProjectInfo

insights_models.proto:42

Used in: FilterInput, PackageReport

enum InsightProjectInfo.Type

insights_models.proto:43

Used in: InsightProjectInfo

message InsightScorecard

insights_models.proto:37

Used in: FilterInput

message InsightVulnerability

insights_models.proto:25

Used in: FilterInputVulnerabilities, PackageReport

message InsightVulnerabilitySeverity

insights_models.proto:5

Used in: InsightVulnerability

enum InsightVulnerabilitySeverity.Risk

insights_models.proto:12

Used in: InsightVulnerabilitySeverity

enum InsightVulnerabilitySeverity.Type

insights_models.proto:6

Used in: InsightVulnerabilitySeverity

message Package

models.proto:25

Used in: PackageManifest, PackageReport, RemediationAdvice, Violation

message PackageManifest

models.proto:31

message PackageManifestReport

json_report_spec.proto:70

Used in: Report

message PackageReport

json_report_spec.proto:82

PackageReport represents the first class entity for which we have different type of reporting information

Used in: Report

message RemediationAdvice

json_report_spec.proto:16

Used in: PackageReport

enum RemediationAdviceType

json_report_spec.proto:9

Used in: RemediationAdvice

message Report

json_report_spec.proto:106

message ReportMeta

json_report_spec.proto:100

Used in: Report

message ReportThreat

json_report_spec.proto:32

We are introducing the concept of Threat as a reporting entity so that we can report threats like lockfile poisoning using a standard schema. But why do we need threats? Why not just use vet's paradigm of policy over enriched packages? The reason is, there are threats that are applicable in an environment, against a manifest or other entities or even group of entities. Hence it is required to introduce a threat as a reporting entity so that external tools can consume vet's reports and take actions based on the threats.

Used in: PackageManifestReport, PackageReport

enum ReportThreat.Confidence

json_report_spec.proto:33

Used in: ReportThreat

enum ReportThreat.ReportThreatId

json_report_spec.proto:54

Used in: ReportThreat

enum ReportThreat.Source

json_report_spec.proto:41

Used in: ReportThreat

enum ReportThreat.SubjectType

json_report_spec.proto:47

Used in: ReportThreat

message Violation

violations.proto:9

Used in: PackageReport