@pagopa/io-app-design-system
The library defining the core components of the design system of @pagopa/io-app
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established, widely-used library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:auto-changelog | AI (phantom-deps): auto-changelog is used in release-it config scripts, not imported in source; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-native-easing-gradient | AI (phantom-deps): Platform-specific binary package; not directly imported in JS but used at runtime; stable false positive. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 8.1.0 | 10 / 41 | |
| 8.0.1 | 10 / 41 | |
| 8.0.0 | 10 / 41 | |
| 7.2.0 | 10 / 40 | |
| 7.1.1 | 10 / 40 | |
| 7.1.0 | 10 / 40 | |
| 7.0.2 | 10 / 41 | |
| 7.0.1 | 10 / 41 | |
| 7.0.0 | 10 / 41 | |
| 6.1.0 | 10 / 40 | |
| 6.0.7 | 9 / 39 | |
| 6.0.6 | 10 / 40 | |
| 6.0.5 | 10 / 40 | |
| 6.0.4 | 10 / 40 | |
| 6.0.1 | 10 / 40 | |
| 6.0.0 | 10 / 40 | |
| 5.12.3 | 9 / 40 | |
| 5.12.2 | 9 / 40 | |
| 5.12.1 | 9 / 40 | |
| 5.12.0 | 9 / 40 | |
| 5.11.19 | 9 / 40 | |
| 5.11.18 | 9 / 40 | |
| 5.11.17 | 9 / 40 | |
| 5.11.16 | 9 / 40 | |
| 5.11.15 | 9 / 40 | |
| 5.11.14 | 9 / 40 | |
| 5.11.13 | 9 / 40 | |
| 5.11.12 | 9 / 40 | |
| 5.11.11 | 9 / 40 |
v7.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (pagopa-bot) on 2026-02-25, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.