@xapp/stentor-service-search
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 — 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-peer-dep:stentor-media | AI (dependencies): Peer dep accepted in prior versions; stable constraint. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 1396 versions; provenance is a future-state improvement, not a blocker. | ai | |
| dependencies | unvetted-dep:http-aws-es | AI (dependencies): http-aws-es is a known AWS Elasticsearch HTTP connector; stable dependency for this package's search service purpose. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; sparse metadata is consistent across the @xapp/stentor-* family. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 1.85.1 | 2 / 6 | |
| 1.80.3 | 2 / 6 | |
| 1.80.1 | 2 / 6 | |
| 1.78.5 | 2 / 6 | |
| 1.78.2 | 2 / 6 | |
| 1.78.0 | 2 / 6 | |
| 1.77.2 | 2 / 6 | |
| 1.76.22 | 2 / 6 | |
| 1.76.20 | 2 / 6 | |
| 1.76.17 | 2 / 6 | |
| 1.76.16 | 2 / 6 | |
| 1.76.12 | 2 / 6 | |
| 1.76.10 | 2 / 6 | |
| 1.76.9 | 2 / 6 | |
| 1.76.6 | 2 / 6 | |
| 1.76.5 | 2 / 6 | |
| 1.76.4 | 2 / 6 | |
| 1.76.3 | 2 / 6 | |
| 1.76.1 | 2 / 6 | |
| 1.74.23 | 2 / 6 | |
| 1.74.22 | 2 / 6 | |
| 1.74.18 | 2 / 6 | |
| 1.74.13 | 2 / 6 | |
| 1.74.9 | 2 / 7 | |
| 1.73.19 | 2 / 7 | |
| 1.73.11 | 2 / 7 | |
| 1.73.6 | 2 / 7 | |
| 1.72.11 | 2 / 7 | |
| 1.72.8 | 2 / 7 | |
| 1.72.7 | 2 / 7 | |
| 1.72.5 | 2 / 7 | |
| 1.72.3 | 2 / 7 | |
| 1.71.29 | 2 / 7 | |
| 1.71.27 | 2 / 7 | |
| 1.71.24 | 2 / 7 | |
| 1.71.23 | 2 / 7 | |
| 1.71.21 | 2 / 7 | |
| 1.71.18 | 2 / 7 | |
| 1.71.12 | 2 / 7 | |
| 1.71.11 | 2 / 7 | |
| 1.71.8 | 2 / 7 | |
| 1.71.4 | 2 / 7 | |
| 1.71.1 | 2 / 7 | |
| 1.70.47 | 2 / 7 | |
| 1.70.44 | 2 / 7 | |
| 1.70.35 | 2 / 7 | |
| 1.70.19 | 2 / 7 | |
| 1.70.16 | 2 / 7 | |
| 1.70.13 | 2 / 7 | |
| 1.70.9 | 2 / 7 | |
| 1.70.6 | 2 / 7 | |
| 1.69.4 | 2 / 7 | |
| 1.69.2 | 2 / 7 | |
| 1.69.1 | 2 / 7 | |
| 1.68.1 | 2 / 7 | |
| 1.66.9 | 2 / 7 | |
| 1.65.43 | 2 / 7 | |
| 1.65.41 | 2 / 7 | |
| 1.65.40 | 2 / 7 | |
| 1.65.38 | 2 / 7 | |
| 1.65.35 | 2 / 7 | |
| 1.65.34 | 2 / 7 | |
| 1.65.31 | 2 / 7 | |
| 1.65.29 | 2 / 7 | |
| 1.65.26 | 2 / 7 | |
| 1.65.20 | 2 / 7 |
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.80.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
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.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.13
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.11
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.5
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. Consider requesting the maintainer enable provenance via CI/CD.
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.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.71.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.19
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.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.9
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.38
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.