@podium/podlet
Module for building page fragment servers in a micro frontend architecture.
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:ajv | AI (phantom-deps): ajv is a declared runtime dependency in package.json; phantom-dep heuristic misfires here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.4.2 | 7 / 15 | |
| 5.4.1 | 7 / 15 | |
| 5.4.0 | 7 / 15 | |
| 5.3.4 | 7 / 15 | |
| 5.3.3 | 7 / 15 | |
| 5.3.2 | 7 / 15 | |
| 5.3.1 | 7 / 15 | |
| 5.3.0 | 7 / 15 |
v5.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.