@fiscozen/appointments
Design System Appointments component
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/appointments.js | AI (source-diff): Standard Rolldown/Vite bundle of Vue components; long lines are minified but readable, not obfuscated. | ai | |
| phantom-deps | phantom-dep:@fiscozen/alert | AI (phantom-deps): Same-org design system dep; likely bundled into dist rather than directly imported in source. | ai | |
| phantom-deps | phantom-dep:@fiscozen/radio | AI (phantom-deps): Same-org design system dep; likely bundled into dist rather than directly imported in source. | ai | |
| phantom-deps | phantom-dep:@fiscozen/button | AI (phantom-deps): Same-org design system dep; likely bundled into dist rather than directly imported in source. | ai | |
| phantom-deps | phantom-dep:@fiscozen/container | AI (phantom-deps): Same-org design system dep; likely bundled into dist rather than directly imported in source. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.12 | 4 / 18 | |
| 1.1.11 | 4 / 18 | |
| 1.1.10 | 4 / 18 | |
| 1.1.7 | 4 / 18 | |
| 1.1.0 | 0 / 18 | |
| 1.0.0 | 0 / 18 |
v1.1.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sergioterrasifiscozen) than the most recent previously approved version (panicofr) on 2026-06-10, but sergioterrasifiscozen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sergioterrasifiscozen) than the most recent previously approved version (panicofr) on 2026-06-09, but sergioterrasifiscozen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.10
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (panicofr) than the most recent previously approved version (cbfiscozen) on 2026-06-09, but panicofr is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.