@xapp/stentor-chat-widget
Chat 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 — 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:stentor-guards | AI (dependencies): First-party stentor ecosystem dep; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:stentor-constants | AI (dependencies): First-party stentor ecosystem dep; consistent pattern across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package in a large monorepo; missing repo/keywords/README detail is a metadata gap, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:stentor-guards | AI (phantom-deps): Heuristic false positive; dep is used via config/type references in this monorepo package. | ai | |
| phantom-deps | phantom-dep:stentor-constants | AI (phantom-deps): Same as stentor-guards; config-level reference pattern stable for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.94.0 | 2 / 12 | |
| 1.91.0 | 2 / 12 | |
| 1.88.0 | 2 / 12 | |
| 1.87.2 | 2 / 12 | |
| 1.87.1 | 2 / 12 | |
| 1.87.0 | 2 / 12 | |
| 1.85.1 | 2 / 12 | |
| 1.85.0 | 2 / 12 | |
| 1.82.1 | 2 / 12 | |
| 1.81.5 | 2 / 12 | |
| 1.81.1 | 2 / 12 | |
| 1.81.0 | 2 / 12 | |
| 1.80.0 | 2 / 11 | |
| 1.79.0 | 2 / 11 | |
| 1.78.1 | 2 / 11 | |
| 1.78.0 | 2 / 11 | |
| 1.77.0 | 2 / 11 | |
| 1.76.1 | 2 / 11 |
v1.94.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.87.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.82.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.81.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v1.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.