@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 17 of 117)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.65.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.