@xapp/stentor-service-promio
Service to interface the Promio CRM service
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): Shift to GitHub Actions CI publisher is a normal automation transition, not compromise. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with CI-managed publishing consolidation, no new suspicious maintainer added. | ai | |
| phantom-deps | phantom-dep:lodash.isequal | AI (phantom-deps): Declared in dependencies; referenced in config files. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Declared in dependencies; referenced in config files. Stable pattern for this package. | ai |
Versions (showing 100 of 191)
| Version | Deps | Published |
|---|---|---|
| 1.86.0 | 1 / 13 | |
| 1.85.1 | 1 / 13 | |
| 1.82.0 | 1 / 13 | |
| 1.81.0 | 0 / 13 | |
| 1.80.3 | 0 / 13 | |
| 1.78.5 | 0 / 13 | |
| 1.78.2 | 0 / 13 | |
| 1.78.0 | 0 / 13 | |
| 1.77.2 | 0 / 13 | |
| 1.76.22 | 0 / 13 | |
| 1.76.20 | 0 / 13 | |
| 1.76.16 | 0 / 13 | |
| 1.76.14 | 0 / 13 | |
| 1.76.13 | 0 / 13 | |
| 1.76.12 | 0 / 13 | |
| 1.76.10 | 0 / 13 | |
| 1.76.9 | 0 / 13 | |
| 1.76.8 | 0 / 13 | |
| 1.76.6 | 0 / 13 | |
| 1.76.5 | 0 / 13 | |
| 1.76.4 | 0 / 13 | |
| 1.76.1 | 0 / 13 | |
| 1.74.23 | 0 / 13 | |
| 1.74.22 | 0 / 13 | |
| 1.74.18 | 3 / 13 | |
| 1.74.14 | 3 / 13 | |
| 1.74.9 | 3 / 13 | |
| 1.73.19 | 3 / 13 | |
| 1.73.11 | 3 / 13 | |
| 1.73.6 | 3 / 13 | |
| 1.73.3 | 3 / 13 | |
| 1.72.11 | 3 / 13 | |
| 1.72.8 | 3 / 13 | |
| 1.72.7 | 3 / 13 | |
| 1.72.4 | 3 / 13 | |
| 1.72.3 | 3 / 13 | |
| 1.72.2 | 3 / 13 | |
| 1.72.0 | 3 / 13 | |
| 1.71.29 | 3 / 11 | |
| 1.71.27 | 3 / 11 | |
| 1.71.24 | 3 / 11 | |
| 1.71.23 | 3 / 11 | |
| 1.71.21 | 3 / 11 | |
| 1.71.18 | 3 / 11 | |
| 1.71.12 | 3 / 11 | |
| 1.71.11 | 3 / 11 | |
| 1.71.9 | 3 / 11 | |
| 1.71.8 | 3 / 11 | |
| 1.71.4 | 3 / 11 | |
| 1.71.1 | 3 / 11 | |
| 1.70.50 | 3 / 11 | |
| 1.70.49 | 3 / 11 | |
| 1.70.47 | 3 / 11 | |
| 1.70.46 | 3 / 11 | |
| 1.70.44 | 3 / 11 | |
| 1.70.38 | 3 / 11 | |
| 1.70.35 | 3 / 11 | |
| 1.70.31 | 3 / 11 | |
| 1.70.19 | 3 / 11 | |
| 1.70.18 | 3 / 11 | |
| 1.70.16 | 3 / 11 | |
| 1.70.13 | 3 / 11 | |
| 1.70.9 | 3 / 11 | |
| 1.70.8 | 3 / 11 | |
| 1.70.6 | 3 / 11 | |
| 1.70.5 | 3 / 11 | |
| 1.70.3 | 3 / 11 | |
| 1.69.4 | 3 / 11 | |
| 1.69.2 | 3 / 11 | |
| 1.69.1 | 3 / 11 | |
| 1.69.0 | 3 / 11 | |
| 1.68.1 | 3 / 11 | |
| 1.66.10 | 3 / 11 | |
| 1.66.9 | 3 / 11 | |
| 1.66.8 | 3 / 11 | |
| 1.66.6 | 3 / 11 | |
| 1.66.4 | 3 / 11 | |
| 1.66.3 | 3 / 11 | |
| 1.66.0 | 3 / 11 | |
| 1.65.43 | 3 / 11 | |
| 1.65.41 | 3 / 11 | |
| 1.65.40 | 3 / 11 | |
| 1.65.39 | 3 / 11 | |
| 1.65.38 | 3 / 11 | |
| 1.65.35 | 3 / 11 | |
| 1.65.34 | 3 / 11 | |
| 1.65.33 | 3 / 11 | |
| 1.65.31 | 3 / 11 | |
| 1.65.29 | 3 / 11 | |
| 1.65.28 | 3 / 11 | |
| 1.65.27 | 3 / 11 | |
| 1.65.26 | 3 / 11 | |
| 1.65.21 | 3 / 11 | |
| 1.65.20 | 3 / 11 | |
| 1.65.17 | 3 / 11 | |
| 1.65.16 | 3 / 11 | |
| 1.65.11 | 3 / 11 | |
| 1.65.10 | 3 / 11 | |
| 1.65.8 | 3 / 11 | |
| 1.65.7 | 3 / 11 |
v1.86.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.