@xapp/stentor-service-sms
PLACEHOLDER DESCRIPTION OF PACKAGE
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Switch to GitHub Actions publisher is a CI migration, not compromise evidence. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is normal for this internal monorepo package. | ai |
Versions (showing 51 of 166)
| Version | Deps | Published |
|---|---|---|
| 1.86.0 | 0 / 15 | |
| 1.85.1 | 0 / 15 | |
| 1.80.3 | 0 / 15 | |
| 1.78.5 | 0 / 15 | |
| 1.78.2 | 0 / 15 | |
| 1.78.0 | 0 / 15 | |
| 1.77.2 | 0 / 15 | |
| 1.76.22 | 0 / 15 | |
| 1.76.20 | 0 / 15 | |
| 1.76.16 | 0 / 15 | |
| 1.76.10 | 0 / 15 | |
| 1.76.9 | 0 / 15 | |
| 1.76.6 | 0 / 15 | |
| 1.76.5 | 0 / 15 | |
| 1.76.4 | 0 / 15 | |
| 1.76.1 | 0 / 15 | |
| 1.74.23 | 0 / 15 | |
| 1.74.22 | 0 / 15 | |
| 1.74.18 | 1 / 15 | |
| 1.74.9 | 1 / 15 | |
| 1.73.19 | 1 / 15 | |
| 1.73.11 | 1 / 15 | |
| 1.73.6 | 1 / 15 | |
| 1.72.11 | 1 / 15 | |
| 1.72.8 | 1 / 15 | |
| 1.72.7 | 1 / 15 | |
| 1.72.4 | 1 / 15 | |
| 1.72.3 | 1 / 15 | |
| 1.71.29 | 1 / 15 | |
| 1.71.27 | 1 / 15 | |
| 1.71.24 | 1 / 15 | |
| 1.71.23 | 1 / 15 | |
| 1.71.21 | 1 / 15 | |
| 1.71.18 | 1 / 15 | |
| 1.71.12 | 1 / 15 | |
| 1.71.11 | 1 / 15 | |
| 1.71.9 | 1 / 15 | |
| 1.71.8 | 1 / 15 | |
| 1.71.4 | 1 / 15 | |
| 1.71.1 | 1 / 15 | |
| 1.70.50 | 1 / 15 | |
| 1.70.49 | 1 / 15 | |
| 1.70.47 | 1 / 15 | |
| 1.70.46 | 1 / 15 | |
| 1.70.44 | 1 / 15 | |
| 1.70.35 | 1 / 15 | |
| 1.70.31 | 1 / 15 | |
| 1.70.19 | 1 / 15 | |
| 1.70.18 | 1 / 15 | |
| 1.70.16 | 1 / 15 | |
| 1.70.9 | 1 / 15 |
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.