@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 — the axios compromise (March 2026) relied on exactly this gap.
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 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.