@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 36 of 136)
| Version | Deps | Published |
|---|---|---|
| 1.62.83 | 5 / 25 | |
| 1.62.75 | 5 / 25 | |
| 1.62.73 | 5 / 25 | |
| 1.62.67 | 5 / 25 | |
| 1.62.65 | 5 / 25 | |
| 1.62.64 | 5 / 25 | |
| 1.62.63 | 5 / 25 | |
| 1.62.61 | 5 / 25 | |
| 1.62.59 | 5 / 25 | |
| 1.62.52 | 5 / 25 | |
| 1.62.37 | 5 / 25 | |
| 1.62.33 | 5 / 25 | |
| 1.62.31 | 5 / 25 | |
| 1.62.26 | 5 / 25 | |
| 1.62.22 | 5 / 25 | |
| 1.62.21 | 5 / 25 | |
| 1.62.17 | 5 / 25 | |
| 1.62.15 | 5 / 25 | |
| 1.62.7 | 5 / 25 | |
| 1.62.1 | 5 / 25 | |
| 1.61.0 | 5 / 25 | |
| 1.60.3 | 5 / 25 | |
| 1.60.0 | 5 / 25 | |
| 1.59.0 | 5 / 25 | |
| 1.58.31 | 5 / 25 | |
| 1.58.28 | 5 / 25 | |
| 1.58.23 | 5 / 25 | |
| 1.58.20 | 5 / 25 | |
| 1.58.17 | 5 / 25 | |
| 1.57.7 | 5 / 25 | |
| 1.57.2 | 5 / 25 | |
| 1.57.1 | 5 / 25 | |
| 1.57.0 | 5 / 25 | |
| 1.56.38 | 5 / 25 | |
| 1.56.37 | 5 / 25 | |
| 1.56.34 | 5 / 25 |
v1.62.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.