← Home

@xapp/stentor-service-contractor-appointments

Service to integrate with Contractor Appointments

46
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): CI-driven publish shift, not an ownership hijack; provenance direction unchanged. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with move to CI publishing, no other malicious signal. ai
provenance no-provenance AI (provenance): Established publisher with clean track record; absence of provenance is common and not a risk signal here. ai
bogus-package bogus-package AI (bogus-package): Part of @xapp/stentor-* monorepo; sparse metadata is consistent across the package family, not indicative of spam. ai

Versions (showing 46 of 46)

Version Deps Published
1.86.0 2 / 10
1.85.1 2 / 10
1.81.0 2 / 10
1.80.3 2 / 10
1.78.7 2 / 10
1.78.2 2 / 10
1.78.0 2 / 10
1.77.2 2 / 10
1.76.23 2 / 10
1.76.22 2 / 10
1.76.20 2 / 10
1.76.16 2 / 10
1.76.10 2 / 10
1.76.9 2 / 10
1.76.6 2 / 10
1.76.5 2 / 10
1.76.4 2 / 10
1.76.1 2 / 10
1.74.23 2 / 10
1.74.22 2 / 10
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.71.0 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.