@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 — 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:@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:@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:actions-on-google | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Referenced in config/type files; 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 | |
| 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 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 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.73.11 | 3 / 24 | |
| 1.65.35 | 5 / 24 | |
| 1.65.33 | 5 / 24 | |
| 1.65.29 | 5 / 24 | |
| 1.65.26 | 5 / 24 | |
| 1.65.20 | 5 / 24 |
v1.85.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.80.3
1 finding[Accepted risk] Package 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.78.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.78.0
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.