@xapp/stentor-service-serviceminder
Service to integrate with Serviceminder
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, not an unknown human account takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org migrating to CI-based publishing, no new suspicious maintainers added. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with 212 versions; no provenance is consistent across all prior releases. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped enterprise package in a large monorepo; sparse metadata is consistent across 212 versions, not a spam indicator. | ai |
Versions (showing 100 of 217)
| Version | Deps | Published |
|---|---|---|
| 1.65.43 | 2 / 10 | |
| 1.65.41 | 2 / 10 | |
| 1.65.40 | 2 / 10 | |
| 1.65.39 | 2 / 10 | |
| 1.65.38 | 2 / 10 | |
| 1.65.37 | 2 / 10 | |
| 1.65.35 | 2 / 10 | |
| 1.65.34 | 2 / 10 | |
| 1.65.33 | 2 / 10 | |
| 1.65.31 | 2 / 10 | |
| 1.65.30 | 2 / 10 | |
| 1.65.29 | 2 / 10 | |
| 1.65.28 | 2 / 10 | |
| 1.65.27 | 2 / 10 | |
| 1.65.26 | 2 / 10 | |
| 1.65.24 | 2 / 10 | |
| 1.65.21 | 2 / 10 | |
| 1.65.20 | 2 / 10 | |
| 1.65.17 | 2 / 10 | |
| 1.65.16 | 2 / 10 | |
| 1.65.12 | 2 / 10 | |
| 1.65.11 | 2 / 10 | |
| 1.65.10 | 2 / 10 | |
| 1.65.9 | 2 / 10 | |
| 1.65.8 | 2 / 10 | |
| 1.65.7 | 2 / 10 | |
| 1.65.4 | 2 / 10 | |
| 1.65.3 | 2 / 10 | |
| 1.64.70 | 2 / 10 | |
| 1.64.69 | 2 / 10 | |
| 1.64.68 | 2 / 10 | |
| 1.64.67 | 2 / 10 | |
| 1.64.65 | 2 / 10 | |
| 1.64.62 | 2 / 10 | |
| 1.64.60 | 2 / 10 | |
| 1.64.59 | 2 / 10 | |
| 1.64.56 | 2 / 10 | |
| 1.64.54 | 2 / 10 | |
| 1.64.52 | 2 / 10 | |
| 1.64.48 | 2 / 10 | |
| 1.64.45 | 2 / 10 | |
| 1.64.40 | 2 / 10 | |
| 1.64.39 | 2 / 10 | |
| 1.64.37 | 2 / 10 | |
| 1.64.34 | 2 / 10 | |
| 1.64.32 | 2 / 10 | |
| 1.64.31 | 2 / 10 | |
| 1.64.29 | 2 / 10 | |
| 1.64.27 | 2 / 10 | |
| 1.64.26 | 2 / 10 | |
| 1.64.24 | 2 / 10 | |
| 1.64.23 | 2 / 10 | |
| 1.64.22 | 2 / 10 | |
| 1.64.20 | 2 / 10 | |
| 1.64.19 | 2 / 10 | |
| 1.64.18 | 2 / 10 | |
| 1.64.14 | 2 / 10 | |
| 1.64.13 | 2 / 10 | |
| 1.64.11 | 2 / 10 | |
| 1.64.10 | 2 / 10 | |
| 1.64.9 | 2 / 10 | |
| 1.64.8 | 2 / 10 | |
| 1.64.7 | 2 / 10 | |
| 1.64.6 | 2 / 10 | |
| 1.64.5 | 2 / 10 | |
| 1.64.4 | 2 / 10 | |
| 1.64.3 | 2 / 10 | |
| 1.63.9 | 2 / 10 | |
| 1.63.8 | 2 / 10 | |
| 1.63.7 | 2 / 10 | |
| 1.63.5 | 2 / 10 | |
| 1.63.4 | 2 / 10 | |
| 1.63.3 | 2 / 10 | |
| 1.63.2 | 2 / 10 | |
| 1.63.1 | 2 / 10 | |
| 1.62.94 | 2 / 10 | |
| 1.62.93 | 2 / 10 | |
| 1.62.91 | 2 / 10 | |
| 1.62.89 | 2 / 10 | |
| 1.62.86 | 2 / 10 | |
| 1.62.85 | 2 / 10 | |
| 1.62.84 | 2 / 10 | |
| 1.62.83 | 2 / 10 | |
| 1.62.81 | 2 / 10 | |
| 1.62.76 | 2 / 10 | |
| 1.62.75 | 2 / 10 | |
| 1.62.73 | 2 / 10 | |
| 1.62.72 | 2 / 10 | |
| 1.62.71 | 2 / 10 | |
| 1.62.69 | 2 / 10 | |
| 1.62.67 | 2 / 10 | |
| 1.62.64 | 2 / 10 | |
| 1.62.63 | 2 / 10 | |
| 1.62.61 | 2 / 10 | |
| 1.62.59 | 2 / 10 | |
| 1.62.56 | 2 / 10 | |
| 1.62.55 | 2 / 10 | |
| 1.62.52 | 2 / 10 | |
| 1.62.47 | 2 / 10 | |
| 1.62.37 | 2 / 10 |
v1.65.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.65.16
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.65.12
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.65.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.65.10
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.65.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.65.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.65.7
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.65.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.65.3
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.70
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.69
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.68
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.67
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.65
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.62
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.60
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.59
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.56
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.54
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.52
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.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.45
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.39
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.34
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.31
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.27
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.23
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.22
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.18
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.10
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.7
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.3
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.63.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.63.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.63.7
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.63.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.63.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.63.3
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.63.2
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.63.1
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.62.94
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.62.93
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.62.91
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.62.89
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.62.86
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.62.85
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.62.84
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.62.83
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.62.81
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.62.76
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.62.75
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.62.73
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.62.72
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.62.71
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.62.69
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.62.67
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.62.64
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.62.63
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.62.61
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.62.59
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.62.56
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.62.55
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.62.52
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.62.47
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.62.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.