@frontify/fondue-components
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance confirms CI/CD publish from official Frontify org; dormancy explained by major version cadence. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): date-fns and react-day-picker are well-known, widely-used packages consistent with adding date-picker UI components. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-radio-group | AI (phantom-deps): Config-file reference; declared and used as runtime dependency. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-tailwindcss | AI (phantom-deps): Config-file reference in linting setup; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-select | AI (phantom-deps): Config-file reference; correctly declared as runtime dependency. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Config-file reference; correctly declared as runtime dependency. | ai | |
| phantom-deps | phantom-dep:tailwind-variants | AI (phantom-deps): Config-file reference; correctly declared as runtime dependency. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 30.6.1 | 23 / 46 | |
| 30.6.0 | 23 / 46 | |
| 30.5.0 | 25 / 46 | |
| 30.4.0 | 25 / 46 | |
| 30.3.0 | 25 / 46 | |
| 30.2.1 | 25 / 46 | |
| 30.2.0 | 25 / 46 | |
| 30.1.0 | 25 / 46 | |
| 30.0.0 | 25 / 46 | |
| 29.2.0 | 25 / 46 | |
| 29.1.0 | 25 / 44 | |
| 29.0.1 | 25 / 44 | |
| 29.0.0 | 25 / 44 | |
| 28.0.0 | 23 / 44 | |
| 27.0.1 | 21 / 44 | |
| 27.0.0 | 21 / 44 | |
| 26.0.3 | 21 / 44 | |
| 26.0.2 | 21 / 44 | |
| 26.0.1 | 21 / 44 | |
| 25.0.0 | 21 / 44 | |
| 24.2.0 | 22 / 43 | |
| 24.1.0 | 22 / 43 | |
| 24.0.0 | 22 / 43 |
v30.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v30.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v30.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v30.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v30.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v30.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v30.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v30.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v30.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v29.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v29.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v29.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v29.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v28.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v27.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v27.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v26.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v26.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v26.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v25.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v24.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.