@@ -17,9 +17,9 @@ represents approximately 80% of software in use according to most surveys.
1717## Package-URL
1818
1919The AboutCode team identified this problem in 2018 in the context of working
20- on our ScanCode and VulnerableCode projects. The solution was and is the PURL
20+ on our ScanCode and VulnerableCode projects. The solution is the PURL
2121(Package-URL) specification which has become the most widely used software
22- identifier for open source software. PURL is now an Ecma standard: [ ECMA-427] ( https://ecma-tc54.github.io/ECMA-427/ ) ,
22+ identifier for open source software. PURL is now an Ecma standard: [ ECMA-427] ( https://ecma-tc54.github.io/ECMA-427/ )
2323and it is on a fast track to become an ISO standard.
2424
2525Our team also identified a related problem - after you have a standard way
@@ -28,7 +28,7 @@ package versions to determine whether a reported vulnerability affects the
2828version that you use? Our solution is the VERS (VErsion Range Specifier)
2929specification which will be submitted to Ecma as a standard in 2026.
3030
31- See the [ Package-URL website ] ( https://package-url.github.io/ www.packageurl.org/ )
31+ See the [ Package-URL] ( https://www.packageurl.org/ ) website
3232for more information about PURL and VERS.
3333
3434See the Package-URL (PURL) projects section of the Home page for more
@@ -38,7 +38,7 @@ capabilities.
3838## Identify software packages and components
3939For the basic use case of identifying software packages and components,
4040AboutCode offers the DejaCode application, ScanCode tools, the PURLDB database
41- and the [ PURL standard ] ( https://package-url.github.io/ www.packageurl.org/docs/purl/purl-spec- introduction ) .
41+ and the [ PURL] ( https://www.packageurl.org/docs/purl/introduction ) standard.
4242
4343- [ DejaCode] ( https://dejacode.readthedocs.io/en/latest/ ) is an enterprise-level
4444application to automate managing your software assets including license
0 commit comments