@podman-desktop/ui-svelte
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:svelte-fa | AI (phantom-deps): Config-referenced peer dependency; stable pattern for this UI library. | ai | |
| dependencies | unvetted-dep:svelte-fa | AI (dependencies): svelte-fa is a well-known Svelte FontAwesome wrapper; stable legitimate dependency for this UI library. | ai | |
| dependencies | unvetted-peer-dep:svelte-fa | AI (dependencies): Same package as above; peer dep usage is expected for this Svelte UI component library. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established scoped package from podman-desktop org; missing description is cosmetic, not a risk signal. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): Svelte component library bundles deps at build time; phantom-dep heuristic is a stable FP here. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-brands-svg-icons | AI (phantom-deps): Same build-time bundling pattern; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Same build-time bundling pattern; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:humanize-duration | AI (phantom-deps): Same build-time bundling pattern; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-free | AI (phantom-deps): Same build-time bundling pattern; stable FP for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.28.3 | 8 / 19 | |
| 1.28.2 | 8 / 19 | |
| 1.27.2 | 8 / 19 | |
| 1.27.1 | 8 / 19 | |
| 1.26.2 | 8 / 19 | |
| 1.26.1 | 8 / 19 | |
| 1.25.1 | 8 / 19 | |
| 1.24.2 | 8 / 19 | |
| 1.24.1 | 8 / 19 | |
| 1.23.1 | 8 / 19 | |
| 1.22.1 | 7 / 19 | |
| 1.22.0 | 7 / 19 | |
| 1.21.0 | 7 / 19 | |
| 1.20.2 | 7 / 19 | |
| 1.20.1 | 7 / 19 | |
| 1.20.0 | 7 / 19 | |
| 1.19.2 | 7 / 19 | |
| 1.19.1 | 7 / 19 | |
| 1.18.1 | 7 / 19 | |
| 1.18.0 | 7 / 19 | |
| 1.17.2 | 7 / 19 | |
| 1.17.1 | 7 / 19 | |
| 1.17.0 | 7 / 19 | |
| 1.16.2 | 7 / 19 | |
| 1.16.1 | 7 / 21 | |
| 1.16.0 | 7 / 21 | |
| 1.15.0 | 7 / 21 | |
| 1.14.2 | 7 / 21 | |
| 1.14.1 | 7 / 21 | |
| 1.14.0 | 7 / 21 | |
| 1.13.3 | 7 / 21 | |
| 1.13.2 | 7 / 21 | |
| 1.12.0 | 7 / 22 | |
| 1.11.1 | 7 / 22 | |
| 1.11.0 | 7 / 22 |
v1.28.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.20.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.20.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.