-
Notifications
You must be signed in to change notification settings - Fork 359
Open
Labels
modelAbout the data modelAbout the data modelocctetIssues that are relevant for https://occtet.eu/Issues that are relevant for https://occtet.eu/
Description
Originating from this comment (and a later update), the NTIA minimum elements calls out for supplier information, and both CycloneDX and SPDX provide according fields. However, there is no strict definition of that the "supplier" of an Open Source package should be. In particular, the "supplier" should not be the hosting website of a package.
That said, I'm proposing the following logic to deduce the supplier (try in order, first match wins):
- For package managers that support it, use the organization name or similar (see e.g. Maven).
- Use the namespace of a package if it contains "com" or "org" and is not a recognized VcsHost.
- Use the author / developer if there's only a single one; prefer its organization (if supported by the package manager, see e.g. Maven) over its name.
Implementing this probably requires to introduce a dedicated "organization" field to the Package model; currently, e.g. the Maven-provided organization is simply added to the set of authors.
tsteenbe and fviernau
Metadata
Metadata
Assignees
Labels
modelAbout the data modelAbout the data modelocctetIssues that are relevant for https://occtet.eu/Issues that are relevant for https://occtet.eu/
Type
Projects
Status
Q1 2026 - Jan-Mar