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
When a package gets renamed (new namespace or name or both), it would be nice to specify the old names as an alias to allow downstream tools to link and maintain history.
Example:
Assume a package @appthreat/cdxgen @ 0.9.0 gets migrated to @cyclonedx/cdxgen @ 1.0.0 from version 1.0.0 onwards
Currently, these would create separate purls without a definitive way of linking them.
When a package gets renamed (new namespace or name or both), it would be nice to specify the old names as an alias to allow downstream tools to link and maintain history.
Example:
Assume a package
@appthreat/cdxgen @ 0.9.0
gets migrated to@cyclonedx/cdxgen @ 1.0.0
from version 1.0.0 onwardsCurrently, these would create separate purls without a definitive way of linking them.
Under the proposal, the new purl could retain the aliases in encoded forms.
Example 1: Single alias
Node.js code snippet for encode
package URL example with a single alias
Example 2: Multiple aliases (appthreat/cdxgen was originally prabhu/cdxgen)
The text was updated successfully, but these errors were encountered: