@plasmicpkgs/plasmic-calendly
Plasmic Calendly 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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package from established Plasmic publisher; sparse metadata is consistent across all plasmicpkgs. | ai | |
| phantom-deps | phantom-dep:change-case | AI (phantom-deps): change-case is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 0.0.101 | 2 / 8 | |
| 0.0.100 | 2 / 8 | |
| 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 / 10 | |
| 0.0.70 | 2 / 10 | |
| 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 |
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
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.