← Home

@xapp/stentor-service-fieldpulse

Service to integrate with FieldPulse

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
provenance publisher-changed AI (provenance): Switch to GitHub Actions CI publisher is a normal automation migration, not compromise. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with CI-managed publishing consolidating maintainer list; no other malicious signal. ai
provenance no-provenance AI (provenance): Established @xapp scoped package with long history; lack of provenance is common and not a risk signal here. ai

Versions (showing 51 of 121)

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

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.