@xapp/stentor-facebook
Facebook 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): Legitimate Google library, long-standing direct dep of this Facebook channel integration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org migrating to automated CI publishing of this monorepo package. | ai | |
| provenance | publisher-changed | AI (provenance): Change reflects move to CI/CD (GitHub Actions) publishing, a positive shift not a compromise indicator. | ai | |
| phantom-deps | phantom-dep:@xapp/stentor-actions-on-google | AI (phantom-deps): Same org scope; consistent false positive pattern for this package family. | ai | |
| phantom-deps | phantom-dep:actions-on-google | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xapp/stentor-app | AI (phantom-deps): Same-org monorepo dep; declared as runtime dependency, phantom-dep heuristic is a false positive here. | ai | |
| dependencies | unvetted-dep:@xapp/patterns | AI (dependencies): Internal @xapp-namespace dependency consistent with this package's ecosystem; stable pattern across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Long-lived monorepo component; sparse metadata is a consistent pattern across all 755 versions, not a spam indicator. | ai |
Versions (showing 62 of 162)
| Version | Deps | Published |
|---|---|---|
| 1.64.24 | 5 / 21 | |
| 1.64.19 | 5 / 21 | |
| 1.64.11 | 5 / 21 | |
| 1.64.9 | 5 / 21 | |
| 1.64.8 | 5 / 21 | |
| 1.64.6 | 5 / 21 | |
| 1.64.4 | 5 / 21 | |
| 1.63.9 | 5 / 21 | |
| 1.63.5 | 5 / 21 | |
| 1.63.4 | 5 / 21 | |
| 1.63.3 | 5 / 21 | |
| 1.63.1 | 5 / 21 | |
| 1.62.94 | 5 / 21 | |
| 1.62.89 | 5 / 21 | |
| 1.62.86 | 5 / 21 | |
| 1.62.85 | 5 / 21 | |
| 1.62.83 | 5 / 21 | |
| 1.62.75 | 5 / 21 | |
| 1.62.73 | 5 / 21 | |
| 1.62.72 | 5 / 21 | |
| 1.62.71 | 5 / 21 | |
| 1.62.67 | 5 / 21 | |
| 1.62.64 | 5 / 21 | |
| 1.62.63 | 5 / 21 | |
| 1.62.61 | 5 / 21 | |
| 1.62.59 | 5 / 21 | |
| 1.62.55 | 5 / 21 | |
| 1.62.52 | 5 / 21 | |
| 1.62.37 | 5 / 21 | |
| 1.62.36 | 5 / 21 | |
| 1.62.32 | 5 / 21 | |
| 1.62.30 | 5 / 21 | |
| 1.62.26 | 5 / 21 | |
| 1.62.22 | 5 / 21 | |
| 1.62.20 | 5 / 21 | |
| 1.62.19 | 5 / 21 | |
| 1.62.16 | 5 / 21 | |
| 1.62.15 | 5 / 21 | |
| 1.62.14 | 5 / 21 | |
| 1.62.10 | 5 / 21 | |
| 1.62.7 | 5 / 21 | |
| 1.62.1 | 5 / 21 | |
| 1.61.0 | 5 / 21 | |
| 1.60.3 | 5 / 21 | |
| 1.60.0 | 5 / 21 | |
| 1.59.0 | 5 / 21 | |
| 1.58.25 | 5 / 21 | |
| 1.58.20 | 5 / 21 | |
| 1.58.16 | 5 / 21 | |
| 1.58.15 | 5 / 21 | |
| 1.58.12 | 5 / 21 | |
| 1.58.4 | 5 / 21 | |
| 1.58.1 | 5 / 21 | |
| 1.58.0 | 5 / 21 | |
| 1.57.7 | 5 / 21 | |
| 1.57.2 | 5 / 21 | |
| 1.57.1 | 5 / 21 | |
| 1.57.0 | 5 / 21 | |
| 1.56.45 | 5 / 21 | |
| 1.56.43 | 5 / 21 | |
| 1.56.38 | 5 / 21 | |
| 1.56.37 | 5 / 21 |
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.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.11
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.6
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.9
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.63.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.94
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.
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.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.71
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.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.55
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.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.30
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.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.16
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.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.10
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.25
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.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
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.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.43
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.