@plasmicpkgs/plasmic-typeform
Plasmic Typeform 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:change-case | AI (phantom-deps): change-case is declared in dependencies; phantom-dep heuristic is a false positive for this package. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.0.99 | 2 / 8 | |
| 0.0.98 | 2 / 8 | |
| 0.0.97 | 2 / 8 | |
| 0.0.96 | 2 / 8 | |
| 0.0.95 | 2 / 8 | |
| 0.0.94 | 2 / 8 | |
| 0.0.93 | 2 / 8 | |
| 0.0.92 | 2 / 8 | |
| 0.0.91 | 2 / 8 | |
| 0.0.90 | 2 / 8 | |
| 0.0.89 | 2 / 8 | |
| 0.0.88 | 2 / 8 | |
| 0.0.87 | 2 / 8 | |
| 0.0.86 | 2 / 8 | |
| 0.0.85 | 2 / 8 | |
| 0.0.84 | 2 / 8 | |
| 0.0.83 | 2 / 8 | |
| 0.0.82 | 2 / 8 | |
| 0.0.81 | 2 / 8 | |
| 0.0.80 | 2 / 8 | |
| 0.0.79 | 2 / 8 | |
| 0.0.78 | 2 / 8 | |
| 0.0.77 | 2 / 8 | |
| 0.0.76 | 2 / 8 | |
| 0.0.75 | 2 / 8 | |
| 0.0.74 | 2 / 8 | |
| 0.0.73 | 2 / 8 | |
| 0.0.72 | 2 / 8 | |
| 0.0.71 | 2 / 8 | |
| 0.0.70 | 2 / 8 | |
| 0.0.69 | 2 / 10 | |
| 0.0.68 | 2 / 10 | |
| 0.0.67 | 2 / 10 | |
| 0.0.66 | 2 / 10 | |
| 0.0.65 | 2 / 10 | |
| 0.0.64 | 2 / 10 | |
| 0.0.63 | 2 / 10 | |
| 0.0.62 | 2 / 10 | |
| 0.0.61 | 2 / 10 | |
| 0.0.60 | 2 / 10 | |
| 0.0.59 | 2 / 10 | |
| 0.0.58 | 2 / 10 | |
| 0.0.57 | 2 / 10 | |
| 0.0.56 | 2 / 10 | |
| 0.0.55 | 2 / 10 | |
| 0.0.54 | 2 / 10 | |
| 0.0.53 | 2 / 10 | |
| 0.0.52 | 2 / 10 | |
| 0.0.51 | 2 / 10 | |
| 0.0.50 | 2 / 10 | |
| 0.0.49 | 2 / 10 | |
| 0.0.48 | 2 / 10 | |
| 0.0.47 | 2 / 10 | |
| 0.0.46 | 2 / 10 | |
| 0.0.45 | 2 / 10 | |
| 0.0.44 | 2 / 10 | |
| 0.0.43 | 2 / 10 | |
| 0.0.42 | 2 / 10 | |
| 0.0.41 | 2 / 10 | |
| 0.0.40 | 2 / 10 | |
| 0.0.39 | 2 / 10 |
v0.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.