@xapp/form-widget
Form Widget
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Referenced in rollup/storybook config; not a direct import but a legitimate peer/build dep. | ai | |
| phantom-deps | phantom-dep:stentor-guards | AI (phantom-deps): Config-file reference in a build tool context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Config-file reference; stable false positive for this MUI-based widget package. | ai | |
| phantom-deps | phantom-dep:lodash.template | AI (phantom-deps): Config-file reference in rollup build setup; stable false positive. | ai | |
| phantom-deps | phantom-dep:@mui/icons-material | AI (phantom-deps): Config-file reference; stable false positive for this MUI-based widget package. | ai | |
| phantom-deps | phantom-dep:autosuggest-highlight | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.94.0 | 11 / 55 | |
| 1.93.0 | 11 / 55 | |
| 1.91.0 | 11 / 55 | |
| 1.90.0 | 11 / 55 | |
| 1.89.1 | 11 / 55 | |
| 1.89.0 | 11 / 55 | |
| 1.88.1 | 11 / 55 | |
| 1.88.0 | 11 / 55 | |
| 1.87.2 | 11 / 54 |
v1.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.88.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.