← Home

@xapp/stentor-service

Base service to be extended for making API calls

100
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

michaelmyersxappbot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Switch to GitHub Actions CI publisher; provenance direction unchanged/improved, not a takeover signal. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with CI-driven publish transition, no other malicious indicators. ai
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:abort-controller 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
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:@xapp/stentor-app AI (phantom-deps): Same-org dep declared in dependencies; phantom-dep heuristic is a false positive 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

Versions (showing 100 of 194)

Version Deps Published
1.86.0 4 / 20
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.12 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.11 10 / 20
1.72.8 10 / 20
1.72.7 10 / 20
1.72.5 10 / 20
1.72.4 10 / 20
1.72.3 10 / 20
1.71.29 10 / 20
1.71.27 10 / 20
1.71.24 10 / 20
1.71.23 10 / 20
1.71.21 10 / 20
1.71.18 10 / 20
1.71.13 10 / 20
1.71.12 10 / 20
1.71.11 10 / 20
1.71.9 10 / 20
1.71.8 10 / 20
1.71.4 10 / 20
1.71.1 10 / 20
1.70.50 10 / 20
1.70.49 10 / 20
1.70.47 10 / 20
1.70.46 10 / 20
1.70.44 10 / 20
1.70.35 10 / 20
1.70.31 10 / 20
1.70.19 10 / 20
1.70.18 10 / 20
1.70.16 10 / 20
1.70.13 10 / 20
1.70.9 10 / 20
1.70.8 10 / 20
1.70.6 10 / 20
1.70.3 10 / 20
1.69.4 10 / 20
1.69.2 10 / 20
1.69.1 10 / 20
1.69.0 10 / 20
1.68.1 10 / 20
1.66.10 10 / 20
1.66.9 10 / 20
1.66.8 10 / 20
1.66.6 10 / 20
1.66.0 10 / 20
1.65.43 10 / 20
1.65.41 10 / 20
1.65.40 10 / 20
1.65.39 10 / 20
1.65.38 10 / 20
1.65.35 10 / 20
1.65.34 10 / 20
1.65.33 10 / 20
1.65.31 10 / 20
1.65.29 10 / 20
1.65.28 10 / 20
1.65.27 10 / 20
1.65.26 10 / 20
1.65.21 10 / 20
1.65.20 10 / 20
1.65.16 10 / 20
1.65.11 10 / 20
1.65.10 10 / 20
1.65.8 10 / 20
1.65.7 10 / 20
1.65.5 10 / 20
1.65.3 10 / 20
1.65.1 10 / 20
1.64.69 10 / 20
1.64.68 10 / 20
1.64.67 10 / 20
1.64.65 10 / 20
Showing 100 of 194 Next page →

v1.86.0

2 findings
HIGH Publisher changed: michaelmyers → GitHub Actions (on 2026-07-16) provenance

This 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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.74.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.72.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.72.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.71.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.71.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.71.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.71.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.71.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.71.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.71.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.50

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.49

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.35

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.19

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.18

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.13

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.70.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.69.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.69.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.68.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.66.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.66.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.66.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.66.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.40

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.39

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.38

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.35

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.33

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.65.31

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.29

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.20

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.16

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.65.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.64.69

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.64.68

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.64.67

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.64.65

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.