@podium/layout
Module for composing full page layouts out of page fragments in a micro frontend architecture.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): ajv is explicitly declared in package.json dependencies; phantom-dep heuristic misfires here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.4.2 | 9 / 16 | |
| 5.4.1 | 9 / 16 | |
| 5.4.0 | 9 / 16 | |
| 5.3.10 | 9 / 16 | |
| 5.3.9 | 9 / 16 | |
| 5.3.8 | 9 / 16 | |
| 5.3.7 | 9 / 16 | |
| 5.3.6 | 9 / 16 | |
| 5.3.5 | 9 / 22 | |
| 5.3.4 | 9 / 22 | |
| 5.3.3 | 9 / 22 | |
| 5.3.2 | 9 / 22 | |
| 5.3.1 | 10 / 22 | |
| 5.3.0 | 10 / 22 | |
| 5.2.20 | 10 / 22 |
v5.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.