@xapp/stentor-form-widget-channel
Form Widget Channel for stentor 📣
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
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): Internal monorepo package; sparse metadata is consistent across the @xapp/stentor family, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:stentor-guards | AI (phantom-deps): Declared dep used in config/type context only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:stentor-constants | AI (phantom-deps): Declared dep used in config/type context only; stable false positive for this package. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.94.1 | 2 / 11 | |
| 1.94.0 | 2 / 11 | |
| 1.91.0 | 2 / 11 | |
| 1.90.0 | 2 / 11 | |
| 1.88.0 | 2 / 11 | |
| 1.87.1 | 2 / 11 | |
| 1.87.0 | 2 / 11 | |
| 1.86.0 | 2 / 11 | |
| 1.85.0 | 2 / 11 | |
| 1.82.1 | 2 / 11 | |
| 1.81.5 | 2 / 11 | |
| 1.81.1 | 2 / 11 | |
| 1.81.0 | 2 / 11 | |
| 1.80.0 | 2 / 11 | |
| 1.79.0 | 2 / 11 | |
| 1.78.0 | 2 / 11 | |
| 1.77.0 | 2 / 11 | |
| 1.76.1 | 2 / 11 | |
| 1.76.0 | 2 / 11 | |
| 1.75.0 | 2 / 11 | |
| 1.74.7 | 2 / 11 | |
| 1.74.6 | 2 / 11 | |
| 1.74.5 | 2 / 11 | |
| 1.74.1 | 2 / 11 | |
| 1.74.0 | 2 / 11 | |
| 1.73.0 | 2 / 11 | |
| 1.72.4 | 2 / 11 | |
| 1.72.3 | 2 / 11 | |
| 1.72.1 | 2 / 11 | |
| 1.72.0 | 2 / 11 | |
| 1.71.0 | 2 / 11 | |
| 1.70.2 | 2 / 11 | |
| 1.70.1 | 2 / 11 | |
| 1.69.0 | 2 / 11 | |
| 1.68.0 | 2 / 11 | |
| 1.65.6 | 2 / 11 | |
| 1.65.0 | 2 / 11 | |
| 1.64.1 | 2 / 11 | |
| 1.64.0 | 2 / 11 | |
| 1.62.0 | 2 / 11 |
v1.94.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-22. 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.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.