@xapp/stentor-intelligent-search-channel
Intelligent Search 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 — 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): Mature package with 71 versions; no provenance is consistent across the entire stentor ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package with 71 published versions; sparse metadata is a stable pattern, not spam. | ai | |
| phantom-deps | phantom-dep:stentor-guards | AI (phantom-deps): Declared dep used in config/build tooling; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:stentor-constants | AI (phantom-deps): Same as stentor-guards; config-referenced dep, stable false positive. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.94.0 | 2 / 11 | |
| 1.91.0 | 2 / 11 | |
| 1.88.0 | 2 / 11 | |
| 1.87.1 | 2 / 11 | |
| 1.87.0 | 2 / 11 | |
| 1.85.0 | 2 / 11 | |
| 1.82.1 | 2 / 11 | |
| 1.81.5 | 2 / 11 | |
| 1.81.1 | 2 / 11 | |
| 1.81.0 | 2 / 11 | |
| 1.80.0 | 2 / 11 | |
| 1.79.0 | 2 / 11 | |
| 1.78.0 | 2 / 11 | |
| 1.77.0 | 2 / 11 | |
| 1.76.1 | 2 / 11 |
v1.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.85.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.82.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.79.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.76.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.