@xapp/stentor-service-fieldpulse
Service to integrate with FieldPulse
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 21 of 121)
| Version | Deps | Published |
|---|---|---|
| 1.64.48 | 1 / 11 | |
| 1.64.40 | 1 / 11 | |
| 1.64.37 | 1 / 11 | |
| 1.64.33 | 1 / 11 | |
| 1.64.32 | 1 / 11 | |
| 1.64.29 | 1 / 11 | |
| 1.64.26 | 1 / 11 | |
| 1.64.24 | 1 / 11 | |
| 1.64.20 | 1 / 11 | |
| 1.64.19 | 1 / 11 | |
| 1.64.17 | 1 / 11 | |
| 1.64.15 | 1 / 11 | |
| 1.64.14 | 1 / 11 | |
| 1.64.13 | 1 / 11 | |
| 1.64.11 | 1 / 11 | |
| 1.64.9 | 1 / 11 | |
| 1.64.8 | 1 / 11 | |
| 1.64.6 | 1 / 11 | |
| 1.64.5 | 1 / 11 | |
| 1.64.4 | 1 / 11 | |
| 1.64.0 | 1 / 11 |
v1.64.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.