← Home

@xapp/stentor-service-housecall-pro

Service to integrate with Housecall Pro

51
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
maintainer-change maintainer-removed AI (maintainer-change): Org-internal package; maintainer list churn without other malicious signals. ai
provenance no-provenance AI (provenance): Established @xapp scoped package with long history; lack of Sigstore attestation is consistent across all versions. ai
bogus-package bogus-package AI (bogus-package): Internal scoped enterprise package with 255 versions; sparse metadata is consistent across all versions, not a spam indicator. ai

Versions (showing 51 of 231)

View all versions
Version Deps Published
1.86.0 4 / 9
1.85.1 4 / 9
1.82.0 4 / 9
1.80.3 3 / 9
1.78.7 3 / 9
1.78.2 3 / 9
1.78.0 3 / 9
1.77.2 3 / 9
1.76.23 3 / 9
1.76.22 3 / 9
1.76.20 3 / 9
1.76.16 3 / 9
1.76.10 3 / 9
1.76.9 3 / 9
1.76.6 3 / 9
1.76.5 3 / 9
1.76.4 3 / 9
1.76.1 3 / 9
1.74.23 3 / 9
1.74.22 3 / 9
1.74.18 2 / 10
1.74.13 2 / 10
1.74.9 2 / 10
1.74.3 2 / 10
1.73.19 2 / 10
1.73.16 2 / 10
1.73.11 2 / 10
1.73.6 2 / 10
1.72.11 2 / 10
1.72.8 2 / 10
1.72.7 2 / 10
1.72.4 2 / 10
1.72.3 2 / 10
1.71.29 2 / 10
1.71.27 2 / 10
1.71.24 2 / 10
1.71.23 2 / 10
1.71.21 2 / 10
1.71.18 2 / 10
1.71.12 2 / 10
1.71.11 2 / 10
1.71.9 2 / 10
1.71.8 2 / 10
1.71.4 2 / 10
1.71.1 2 / 10
1.70.50 2 / 10
1.70.49 2 / 10
1.70.47 2 / 10
1.70.46 2 / 10
1.70.44 2 / 10
1.70.38 2 / 10

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.