@calcom/atoms
Customizable UI components to integrate scheduling into your product.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:react-digit-input | AI (dependencies): react-digit-input is a benign React input component; stable false positive for this UI library. | ai | |
| provenance | no-provenance | AI (provenance): Established Cal.com package; provenance absence is consistent across all prior versions. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large bundled component library; file count growth reflects legitimate feature expansion, not injected code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All 5 new deps are established UI utilities consistent with this scheduling component library's purpose. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-tooltip-atoms | AI (dependencies): npm alias for @radix-ui/[email protected]; standard version-pinning pattern. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Build/config-file reference in a UI component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Build/config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-popover-atoms | AI (dependencies): npm alias for @radix-ui/[email protected]; standard version-pinning pattern. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-dialog-atoms | AI (dependencies): npm alias for @radix-ui/[email protected]; standard version-pinning pattern, not a suspicious package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.10.1 | 19 / 59 | |
| 2.10.0 | 19 / 59 | |
| 2.9.1 | 19 / 59 | |
| 2.9.0 | 19 / 59 | |
| 2.8.6 | 19 / 59 | |
| 2.8.5 | 19 / 59 | |
| 2.8.3 | 14 / 58 | |
| 2.8.2 | 47 / 26 | |
| 2.8.1 | 47 / 26 | |
| 2.7.2 | 47 / 26 | |
| 2.6.0 | 14 / 23 | |
| 2.4.0 | 14 / 23 |
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.