@xapp/stentor-gbm — Greenflagged

Google Business Messages channel for stentor

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

michaelmyersxappbot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@xapp/patterns	AI (dependencies): Same-org scoped dependency, consistent across stentor family releases.	ai	2026/07/16
provenance	publisher-changed	AI (provenance): CI/CD publisher transition, not manual account change; no other malicious signal.	ai	2026/07/16
maintainer-change	maintainer-removed	AI (maintainer-change): Consistent with org's CI migration, no takeover behavior evidenced.	ai	2026/07/16
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	2026/05/21
phantom-deps	phantom-dep:googleapis-common	AI (phantom-deps): Referenced in config files per finding; stable false positive for this package.	ai	2026/05/21
bogus-package	bogus-package	AI (bogus-package): Scoped monorepo package with 468 versions; sparse metadata is typical for internal ecosystem packages.	ai	2026/05/01

Versions (showing 2 of 202)

Version	Deps	Published
1.56.34	7 / 24	2024-05-08
1.56.30	7 / 24	2024-05-06

v1.56.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.56.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.