@xapp/stentor-slack
Slack channel for stentor
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:actions-on-google | AI (dependencies): Well-known Google Actions SDK, long-standing direct dependency. | ai | |
| provenance | publisher-changed | AI (provenance): Switch to GitHub Actions CI publisher, not a suspicious manual account change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer list cleanup in long-running internal package. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:actions-on-google | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xapp/stentor-app | AI (phantom-deps): Same org scope; likely used transitively or via re-export in this monorepo package. | ai | |
| phantom-deps | phantom-dep:@xapp/stentor-actions-on-google | AI (phantom-deps): Same org scope; monorepo transitive usage pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal ecosystem package with 426 versions; sparse metadata is a style choice, not a spam indicator. | ai |
Versions (showing 100 of 136)
| Version | Deps | Published |
|---|---|---|
| 1.86.0 | 1 / 24 | |
| 1.85.1 | 1 / 24 | |
| 1.80.3 | 1 / 24 | |
| 1.78.4 | 1 / 24 | |
| 1.78.0 | 1 / 24 | |
| 1.76.22 | 1 / 24 | |
| 1.76.20 | 1 / 24 | |
| 1.76.16 | 1 / 24 | |
| 1.76.15 | 1 / 24 | |
| 1.76.10 | 1 / 24 | |
| 1.76.9 | 1 / 24 | |
| 1.76.6 | 1 / 24 | |
| 1.76.5 | 1 / 24 | |
| 1.76.4 | 1 / 24 | |
| 1.76.1 | 1 / 24 | |
| 1.74.25 | 1 / 24 | |
| 1.74.23 | 1 / 24 | |
| 1.74.22 | 1 / 24 | |
| 1.74.18 | 3 / 25 | |
| 1.74.12 | 3 / 25 | |
| 1.74.9 | 3 / 25 | |
| 1.73.19 | 3 / 25 | |
| 1.73.11 | 3 / 25 | |
| 1.73.6 | 3 / 25 | |
| 1.72.11 | 3 / 25 | |
| 1.72.8 | 3 / 25 | |
| 1.72.7 | 3 / 25 | |
| 1.72.5 | 3 / 25 | |
| 1.72.4 | 3 / 25 | |
| 1.72.3 | 3 / 25 | |
| 1.71.29 | 3 / 25 | |
| 1.71.27 | 3 / 25 | |
| 1.71.24 | 3 / 25 | |
| 1.71.23 | 3 / 25 | |
| 1.71.21 | 3 / 25 | |
| 1.71.18 | 3 / 25 | |
| 1.71.13 | 3 / 25 | |
| 1.71.12 | 3 / 25 | |
| 1.71.11 | 3 / 25 | |
| 1.71.9 | 3 / 25 | |
| 1.71.8 | 3 / 25 | |
| 1.71.4 | 3 / 25 | |
| 1.71.1 | 3 / 25 | |
| 1.70.50 | 3 / 25 | |
| 1.70.49 | 3 / 25 | |
| 1.70.47 | 3 / 25 | |
| 1.70.46 | 3 / 25 | |
| 1.70.44 | 3 / 25 | |
| 1.70.35 | 3 / 25 | |
| 1.70.31 | 3 / 25 | |
| 1.70.26 | 3 / 25 | |
| 1.70.19 | 3 / 25 | |
| 1.70.18 | 3 / 25 | |
| 1.70.16 | 3 / 25 | |
| 1.70.13 | 3 / 25 | |
| 1.70.9 | 3 / 25 | |
| 1.70.8 | 3 / 25 | |
| 1.70.6 | 3 / 25 | |
| 1.70.3 | 3 / 25 | |
| 1.69.4 | 3 / 25 | |
| 1.69.2 | 3 / 25 | |
| 1.69.1 | 3 / 25 | |
| 1.69.0 | 3 / 25 | |
| 1.68.1 | 3 / 25 | |
| 1.66.10 | 3 / 25 | |
| 1.66.9 | 3 / 25 | |
| 1.66.8 | 3 / 25 | |
| 1.66.7 | 3 / 25 | |
| 1.66.6 | 5 / 25 | |
| 1.65.41 | 5 / 25 | |
| 1.65.40 | 5 / 25 | |
| 1.65.35 | 5 / 25 | |
| 1.65.34 | 5 / 25 | |
| 1.65.33 | 5 / 25 | |
| 1.65.31 | 5 / 25 | |
| 1.65.27 | 5 / 25 | |
| 1.65.26 | 5 / 25 | |
| 1.65.21 | 5 / 25 | |
| 1.65.20 | 5 / 25 | |
| 1.65.10 | 5 / 25 | |
| 1.65.7 | 5 / 25 | |
| 1.65.3 | 5 / 25 | |
| 1.65.1 | 5 / 25 | |
| 1.64.69 | 5 / 25 | |
| 1.64.67 | 5 / 25 | |
| 1.64.65 | 5 / 25 | |
| 1.64.64 | 5 / 25 | |
| 1.64.34 | 5 / 25 | |
| 1.64.32 | 5 / 25 | |
| 1.64.26 | 5 / 25 | |
| 1.64.24 | 5 / 25 | |
| 1.64.9 | 5 / 25 | |
| 1.64.8 | 5 / 25 | |
| 1.64.7 | 5 / 25 | |
| 1.64.4 | 5 / 25 | |
| 1.63.5 | 5 / 25 | |
| 1.62.96 | 5 / 25 | |
| 1.62.89 | 5 / 25 | |
| 1.62.86 | 5 / 25 | |
| 1.62.85 | 5 / 25 |
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.74.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.66.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.27
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. 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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.