Skip to content

Issues: package-url/purl-spec

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
98 Open 69 Closed
98 Open 69 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

App Stores
#327 opened Sep 8, 2024 by tonylturner updated Sep 20, 2024
2
Support for vscode type
#287 opened Jan 30, 2024 by prabhu updated Sep 7, 2024
3
Clarify the formal requirement on max length
#289 opened Feb 6, 2024 by prabhu updated Sep 2, 2024
2
Google Git PURL type
#326 opened Aug 28, 2024 by jsdratm updated Aug 28, 2024
The CPAN urls with :: doesn't pass syntax check in Python lib
#324 opened Aug 27, 2024 by oej updated Aug 28, 2024
4
Percent encoding spec and : and / PURL core specification Format and syntax that define PURL (excludes PURL type definitions)
#39 opened Apr 6, 2018 by jdillon updated Aug 20, 2024 1.0
13
RPM Namespace is Ambiguous, Need Clarity
#239 opened Jun 27, 2023 by dariush-griffin updated Aug 16, 2024
2
Make a versioned release and have pkg:package-url/purl-spec@1.0.0
#319 opened Aug 7, 2024 by bact updated Aug 7, 2024
Reserve LabVIEW-related package formats vip / nipkg
#202 opened Nov 9, 2022 by samsharp99 updated Aug 7, 2024
3
Is "PURL" (all caps) considered an incorrect abbreviation?
#280 opened Dec 4, 2023 by joeattardi updated Jul 17, 2024
4
[vers] how to deal with problematic symbols such as brackets
#313 opened Jul 15, 2024 by prabhu updated Jul 15, 2024
Define package types for ASF projects (Apache Software Foundation)
#305 opened Jun 14, 2024 by pombredanne updated Jul 8, 2024
3
[PURL-TYPE: golang] fix type spec regarding path segments
#308 opened Jun 24, 2024 by jkowalleck updated Jul 4, 2024
15
Namespace clarification for third-party Debian/Ubuntu Package
#307 opened Jun 17, 2024 by captn3m0 updated Jul 2, 2024
3
Proposal: Solution for Purl Type Definitions PURL type definition Non-core definitions that describe and standardize PURL types
#310 opened Jun 24, 2024 by stevespringett updated Jun 24, 2024
@stevespringett
2
OCI type: is version required?
#157 opened Mar 17, 2022 by MarkLodato updated Jun 19, 2024
1
Debian Repository URL Format should be clarified
#306 opened Jun 17, 2024 by captn3m0 updated Jun 17, 2024
4
Concerns with type-specific component value transformations PURL core specification Format and syntax that define PURL (excludes PURL type definitions)
#38 opened Apr 6, 2018 by jdillon updated Jun 13, 2024 1.0
5
Version range
#66 opened Oct 16, 2019 by iamwillbar updated Jun 12, 2024
29
Register purl pkg: scheme @ IANA
#124 opened Sep 16, 2021 by pombredanne updated May 15, 2024
@pombredanne
14
Default maven repository
#303 opened May 2, 2024 by prabhu updated May 3, 2024
2
[Proposal] deno, jsr, and esm.sh
#302 opened Apr 29, 2024 by prabhu updated Apr 30, 2024
9
Governance
#190 opened Aug 24, 2022 by iamwillbar updated Apr 25, 2024
1 of 8 tasks
@ashcrow @sschuberth
@pombredanne @iamwillbar @stevespringett
22
Proposal: github-release type
#299 opened Apr 1, 2024 by steiza updated Apr 19, 2024
1
Should we support a leading v in golang packages?
#294 opened Mar 8, 2024 by TG1999 updated Mar 21, 2024
8
ProTip! Add no:assignee to see everything that’s not assigned.