@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 41 of 41)
| 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 | |
| 5.2.4 | 7 / 15 | |
| 5.2.3 | 7 / 15 | |
| 5.2.2 | 7 / 15 | |
| 5.2.1 | 7 / 15 | |
| 5.2.0 | 7 / 15 | |
| 5.1.19 | 7 / 14 | |
| 5.1.18 | 7 / 14 | |
| 5.1.17 | 7 / 21 | |
| 5.1.16 | 7 / 21 | |
| 5.1.15 | 7 / 21 | |
| 5.1.14 | 7 / 21 | |
| 5.1.13 | 7 / 21 | |
| 5.1.12 | 7 / 21 | |
| 5.1.11 | 7 / 21 | |
| 5.1.10 | 7 / 21 | |
| 5.1.9 | 7 / 21 | |
| 5.1.8 | 7 / 21 | |
| 5.1.7 | 7 / 21 | |
| 5.1.6 | 7 / 21 | |
| 5.1.5 | 7 / 21 | |
| 5.1.4 | 7 / 20 | |
| 5.1.3 | 7 / 20 | |
| 5.1.2 | 7 / 20 | |
| 5.1.1 | 7 / 20 | |
| 5.1.0 | 7 / 20 | |
| 5.0.7 | 7 / 19 | |
| 5.0.6 | 7 / 19 | |
| 5.0.5 | 7 / 19 | |
| 5.0.4 | 7 / 19 | |
| 5.0.3 | 7 / 19 | |
| 5.0.2 | 7 / 19 | |
| 5.0.1 | 7 / 19 | |
| 5.0.0 | 7 / 17 |
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.