@xapp/stentor-twilio-sms
Twilio SMS 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org migrating to CI-based publishing. | ai | |
| provenance | publisher-changed | AI (provenance): Switch to GitHub Actions CI publisher, not an individual account takeover. | ai | |
| dependencies | unvetted-dep:@xapp/stentor-app | AI (dependencies): Same org scope (@xapp); stable internal dependency across this package's many versions. | ai | |
| dependencies | unvetted-dep:actions-on-google | AI (dependencies): Well-known Google Actions SDK; not a novel or suspicious dependency for this channel package. | ai | |
| phantom-deps | phantom-dep:actions-on-google | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xapp/stentor-app | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive for this monorepo structure. | ai | |
| phantom-deps | phantom-dep:@xapp/stentor-actions-on-google | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive for this monorepo structure. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Referenced in config/type files; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Entire @xapp/stentor-* monorepo publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal ecosystem package; sparse metadata is consistent across the entire @xapp/stentor monorepo. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 1.86.0 | 1 / 23 | |
| 1.85.1 | 1 / 23 | |
| 1.80.3 | 1 / 23 | |
| 1.78.4 | 1 / 23 | |
| 1.78.2 | 1 / 23 | |
| 1.78.0 | 1 / 23 | |
| 1.77.2 | 1 / 23 | |
| 1.76.22 | 1 / 23 | |
| 1.76.20 | 1 / 23 | |
| 1.76.16 | 1 / 23 | |
| 1.76.15 | 1 / 23 | |
| 1.76.10 | 1 / 23 | |
| 1.76.9 | 1 / 23 | |
| 1.76.6 | 1 / 23 | |
| 1.76.5 | 1 / 23 | |
| 1.76.4 | 1 / 23 | |
| 1.76.1 | 1 / 23 | |
| 1.74.25 | 1 / 23 | |
| 1.74.23 | 1 / 23 | |
| 1.74.22 | 1 / 23 | |
| 1.74.18 | 3 / 24 | |
| 1.74.12 | 3 / 24 | |
| 1.74.9 | 3 / 24 | |
| 1.73.19 | 3 / 24 | |
| 1.73.11 | 3 / 24 | |
| 1.73.6 | 3 / 24 | |
| 1.72.11 | 3 / 24 | |
| 1.72.8 | 3 / 24 | |
| 1.72.7 | 3 / 24 | |
| 1.72.5 | 3 / 24 | |
| 1.72.4 | 3 / 24 | |
| 1.72.3 | 3 / 24 | |
| 1.71.29 | 3 / 24 | |
| 1.71.27 | 3 / 24 | |
| 1.71.24 | 3 / 24 | |
| 1.71.23 | 3 / 24 | |
| 1.71.21 | 3 / 24 | |
| 1.71.18 | 3 / 24 | |
| 1.71.13 | 3 / 24 | |
| 1.71.12 | 3 / 24 | |
| 1.71.11 | 3 / 24 | |
| 1.71.9 | 3 / 24 | |
| 1.71.8 | 3 / 24 | |
| 1.71.4 | 3 / 24 | |
| 1.71.1 | 3 / 24 | |
| 1.70.50 | 3 / 24 | |
| 1.70.49 | 3 / 24 | |
| 1.70.47 | 3 / 24 | |
| 1.70.46 | 3 / 24 | |
| 1.70.44 | 3 / 24 | |
| 1.70.35 | 3 / 24 |
v1.86.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.