@podman-desktop/api Apache-2.0 61 versions

@podman-desktop/api

npm Repository Homepage

API for Podman Desktop extensions

61

Versions

Apache-2.0

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

florentbenoitpodman-desktop-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Official @podman-desktop scoped package; name similarity to hapi is coincidental.	ai	2026/04/29
typosquat	typosquat.levenshtein:pg	AI (typosquat): Official @podman-desktop scoped package; name similarity to pg is coincidental.	ai	2026/04/29
typosquat	typosquat.levenshtein:joi	AI (typosquat): Official @podman-desktop scoped package; name similarity to joi is coincidental.	ai	2026/04/29
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Official @podman-desktop scoped package; name similarity to ajv is coincidental.	ai	2026/04/29

Versions (showing 61 of 61)

Version	Deps	Published
1.28.3	0 / 0	2026-07-20
1.28.2	0 / 0	2026-06-22
1.27.2	0 / 0	2026-05-26
1.27.1	0 / 0	2026-05-20
1.26.2	0 / 0	2026-04-17
1.26.1	0 / 0	2026-03-23
1.25.1	0 / 0	2026-01-26
1.24.2	0 / 0	2025-12-10
1.24.1	0 / 0	2025-12-09
1.23.1	0 / 0	2025-11-13
1.22.1	0 / 0	2025-10-14
1.22.0	0 / 0	2025-09-29
1.21.0	0 / 0	2025-08-19
1.20.2	0 / 0	2025-07-17
1.20.1	0 / 0	2025-07-11
1.20.0	0 / 0	2025-07-07
1.19.2	0 / 0	2025-06-11
1.19.1	0 / 0	2025-05-21
1.18.1	0 / 0	2025-05-08
1.18.0	0 / 0	2025-04-14
1.17.2	0 / 0	2025-03-20
1.17.1	0 / 0	2025-03-03
1.17.0	0 / 0	2025-03-02
1.16.2	0 / 0	2025-02-13
1.16.1	0 / 0	2025-01-31
1.16.0	0 / 0	2025-01-24
1.15.0	0 / 0	2024-12-12
1.14.2	0 / 0	2024-12-04
1.14.1	0 / 0	2024-11-05
1.14.0	0 / 0	2024-10-31
1.13.3	0 / 0	2024-10-23
1.13.2	0 / 0	2024-10-10
1.12.0	0 / 0	2024-08-07
1.11.1	0 / 0	2024-06-24
1.11.0	0 / 0	2024-06-19
1.10.3	0 / 0	2024-05-27
1.10.2	0 / 0	2024-05-02
1.10.1	0 / 0	2024-04-30
1.10.0	0 / 0	2024-04-25
1.9.1	0 / 0	2024-04-04
1.9.0	0 / 0	2024-04-03
1.8.0	0 / 0	2024-03-11
1.7.1	0 / 0	2024-02-06
1.7.0	0 / 0	2024-01-24
1.6.4	0 / 0	2024-01-04
1.6.3	0 / 0	2023-12-15
1.6.2	0 / 0	2023-12-14
1.6.1	0 / 0	2023-12-13
1.6.0	0 / 0	2023-12-11
1.5.3	0 / 0	2023-11-07
1.5.2	0 / 0	2023-11-01
1.5.1	0 / 0	2023-11-01
1.5.0	0 / 0	2023-10-24
1.4.0	0 / 0	2023-09-14
1.3.1	0 / 0	2023-08-17
1.3.0	0 / 0	2023-08-16
1.2.1	0 / 0	2023-07-19
1.2.0	0 / 0	2023-07-12
1.1.0	0 / 0	2023-06-08
1.0.1	0 / 0	2023-05-22
1.0.0	0 / 0	2023-05-17

v1.28.3

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.16.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.