@xapp/stentor-service
Base service to be extended for making API calls
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @xapp org package; provenance absence is consistent across all versions and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): Declared runtime dep; false positive for this package's import style. | ai | |
| phantom-deps | phantom-dep:traverse | AI (phantom-deps): Declared runtime dep; false positive for this package's import style. | ai | |
| phantom-deps | phantom-dep:uuid4 | AI (phantom-deps): Declared runtime dep in package.json; phantom-dep heuristic fires on indirect import patterns common in this monorepo. | ai | |
| phantom-deps | phantom-dep:@xapp/stentor-app | AI (phantom-deps): Same-org dep declared in dependencies; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): 2500+ day old package with 1348 versions; missing metadata is a stable characteristic, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:abort-controller | AI (phantom-deps): Declared runtime dep; false positive for this package's import style. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 1.85.1 | 4 / 20 | |
| 1.80.3 | 4 / 20 | |
| 1.78.5 | 4 / 20 | |
| 1.78.2 | 4 / 20 | |
| 1.78.0 | 4 / 20 | |
| 1.77.2 | 4 / 20 | |
| 1.76.22 | 4 / 20 | |
| 1.76.20 | 4 / 20 | |
| 1.76.17 | 4 / 20 | |
| 1.76.16 | 4 / 20 | |
| 1.76.12 | 4 / 20 | |
| 1.76.10 | 4 / 20 | |
| 1.76.9 | 4 / 20 | |
| 1.76.6 | 4 / 20 | |
| 1.76.5 | 4 / 20 | |
| 1.76.4 | 4 / 20 | |
| 1.76.1 | 4 / 20 | |
| 1.74.25 | 4 / 20 | |
| 1.74.23 | 4 / 20 | |
| 1.74.22 | 4 / 20 | |
| 1.74.18 | 10 / 20 | |
| 1.74.14 | 10 / 20 | |
| 1.74.9 | 10 / 20 | |
| 1.73.19 | 10 / 20 | |
| 1.73.11 | 10 / 20 | |
| 1.73.6 | 10 / 20 | |
| 1.73.3 | 10 / 20 | |
| 1.72.8 | 10 / 20 | |
| 1.72.7 | 10 / 20 | |
| 1.72.4 | 10 / 20 | |
| 1.72.3 | 10 / 20 | |
| 1.71.29 | 10 / 20 | |
| 1.71.27 | 10 / 20 | |
| 1.71.23 | 10 / 20 | |
| 1.71.21 | 10 / 20 | |
| 1.71.18 | 10 / 20 | |
| 1.71.13 | 10 / 20 | |
| 1.70.47 | 10 / 20 | |
| 1.70.46 | 10 / 20 | |
| 1.70.44 | 10 / 20 | |
| 1.70.16 | 10 / 20 | |
| 1.70.8 | 10 / 20 | |
| 1.69.4 | 10 / 20 | |
| 1.69.0 | 10 / 20 | |
| 1.66.6 | 10 / 20 | |
| 1.65.43 | 10 / 20 | |
| 1.65.41 | 10 / 20 | |
| 1.65.34 | 10 / 20 | |
| 1.65.28 | 10 / 20 | |
| 1.65.21 | 10 / 20 |
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.5
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.17
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.74.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.74.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.73.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.