You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/taxonomy.md
+5
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,11 @@ refer to the [official documentation](https://github.com/CycloneDX/cyclonedx-pro
38
38
|`redhat:sbomer:image:labels:vcs-type`| Specifies the type of version control system used, such as Git or SVN. |`components[]`|
39
39
|`redhat:sbomer:image:labels:vendor`| Identifies the organization or individual responsible for a container image. |`components[]`|
40
40
|`redhat:sbomer:image:labels:version`| Denotes the version of the application or component contained within a container image. |`components[]`|
41
+
|`redhat:sbomer:location:0:path`| Indicates the file system path where the package or artifact was found. |`components[]`|
42
+
|`redhat:sbomer:metadata:virtualPath`| Represents a virtual file path that points to a package inside an archive or layered file system. |`components[]`|
43
+
|`redhat:sbomer:package:language`| Specifies the programming language of the detected package. |`components[]`|
44
+
|`redhat:sbomer:package:type`| Defines the type of package, indicating how it was installed or distributed. |`components[]`|
45
+
41
46
42
47
The `Scope` column describes which `properties` section is the intended location for the property. For example,
43
48
a scope of `metadata` means that the property is intended for use in `metadata/properties`. This is meant as a
0 commit comments