@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Minified Rollup bundle, not obfuscation; matches package's build tooling. | ai | |
| source-diff | net-exec-file:dist/index.js | AI (source-diff): Bundled React/UI code, no evidence of dropper/loader behavior. | ai | |
| provenance | publisher-changed | AI (provenance): CI-based publisher switch with no code changes; not account compromise indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-side maintainer list cleanup, no suspicious content changes accompany it. | 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:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:autosuggest-highlight | AI (phantom-deps): Config-file reference; stable false positive for this package. | 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:@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 |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.96.0 | 11 / 55 | |
| 1.95.1 | 11 / 55 | |
| 1.95.0 | 11 / 55 | |
| 1.94.3 | 11 / 55 | |
| 1.94.2 | 11 / 55 | |
| 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 | |
| 1.87.1 | 11 / 54 | |
| 1.87.0 | 11 / 54 | |
| 1.86.0 | 11 / 54 | |
| 1.85.0 | 11 / 54 | |
| 1.84.3 | 11 / 54 | |
| 1.84.1 | 11 / 54 | |
| 1.84.0 | 11 / 54 | |
| 1.83.1 | 11 / 54 | |
| 1.82.1 | 11 / 54 | |
| 1.81.5 | 11 / 54 | |
| 1.81.2 | 11 / 54 | |
| 1.81.1 | 11 / 54 | |
| 1.81.0 | 11 / 54 | |
| 1.80.0 | 11 / 51 |
v1.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.95.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.3
2 findingsThis version was published by a different npm account than previous versions on 2026-07-14. 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.87.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.