@xapp/stentor-gbm
Google Business Messages 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xapp/stentor-app | AI (phantom-deps): Same org monorepo pattern; declared as dep but may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:googleapis-common | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package with 468 versions; sparse metadata is typical for internal ecosystem packages. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.85.1 | 4 / 23 | |
| 1.81.1 | 4 / 23 | |
| 1.80.3 | 4 / 23 | |
| 1.78.4 | 4 / 23 | |
| 1.77.2 | 4 / 23 | |
| 1.76.22 | 4 / 23 | |
| 1.76.20 | 4 / 23 | |
| 1.76.16 | 4 / 23 | |
| 1.76.15 | 4 / 23 | |
| 1.76.10 | 4 / 23 | |
| 1.76.9 | 4 / 23 | |
| 1.76.6 | 4 / 23 | |
| 1.76.5 | 4 / 23 | |
| 1.76.4 | 4 / 23 | |
| 1.76.1 | 4 / 23 | |
| 1.74.25 | 4 / 23 | |
| 1.74.23 | 4 / 23 | |
| 1.74.22 | 4 / 23 | |
| 1.70.35 | 7 / 24 | |
| 1.70.26 | 7 / 24 |
v1.85.1
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.80.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.4
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.
v1.74.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.