@podlite/to-jsx
Render Podlite markup as React JSX components
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): react-is is a declared runtime dependency; phantom-dep heuristic fires because it's used indirectly via React internals. | ai | |
| phantom-deps | phantom-dep:@podlite/diagram | AI (phantom-deps): Same-org package declared as both a dependency and peer dependency; indirect usage pattern is expected in this monorepo. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.0.56 | 6 / 0 | |
| 0.0.55 | 6 / 0 | |
| 0.0.54 | 6 / 0 | |
| 0.0.53 | 6 / 0 | |
| 0.0.52 | 6 / 0 | |
| 0.0.51 | 6 / 0 | |
| 0.0.50 | 5 / 0 | |
| 0.0.49 | 5 / 0 | |
| 0.0.48 | 5 / 0 | |
| 0.0.47 | 5 / 0 | |
| 0.0.46 | 5 / 0 | |
| 0.0.45 | 5 / 0 | |
| 0.0.44 | 5 / 0 | |
| 0.0.43 | 5 / 0 | |
| 0.0.42 | 5 / 0 | |
| 0.0.41 | 5 / 0 | |
| 0.0.40 | 5 / 0 | |
| 0.0.39 | 5 / 0 | |
| 0.0.38 | 5 / 0 | |
| 0.0.37 | 5 / 0 | |
| 0.0.36 | 5 / 0 | |
| 0.0.35 | 5 / 0 | |
| 0.0.34 | 5 / 0 | |
| 0.0.33 | 5 / 0 | |
| 0.0.32 | 5 / 0 | |
| 0.0.31 | 5 / 0 | |
| 0.0.30 | 5 / 0 | |
| 0.0.29 | 5 / 0 | |
| 0.0.28 | 5 / 0 | |
| 0.0.27 | 5 / 0 | |
| 0.0.26 | 5 / 0 | |
| 0.0.25 | 5 / 0 | |
| 0.0.24 | 5 / 0 | |
| 0.0.23 | 5 / 0 | |
| 0.0.22 | 4 / 0 | |
| 0.0.21 | 4 / 0 | |
| 0.0.20 | 4 / 0 | |
| 0.0.19 | 4 / 0 | |
| 0.0.18 | 4 / 0 | |
| 0.0.17 | 4 / 0 | |
| 0.0.16 | 3 / 0 |
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.