@xapp/stentor-chat-widget
Chat Widget 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:stentor-guards | AI (dependencies): First-party stentor ecosystem dep; consistent pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:stentor-constants | AI (dependencies): First-party stentor ecosystem dep; consistent pattern across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package in a large monorepo; missing repo/keywords/README detail is a metadata gap, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:stentor-guards | AI (phantom-deps): Heuristic false positive; dep is used via config/type references in this monorepo package. | ai | |
| phantom-deps | phantom-dep:stentor-constants | AI (phantom-deps): Same as stentor-guards; config-level reference pattern stable for this package. | ai |
Versions (showing 24 of 124)
| Version | Deps | Published |
|---|---|---|
| 1.24.0 | 2 / 12 | |
| 1.23.0 | 2 / 12 | |
| 1.21.3 | 2 / 12 | |
| 1.21.2 | 2 / 12 | |
| 1.21.1 | 2 / 12 | |
| 1.21.0 | 2 / 12 | |
| 1.20.1 | 2 / 12 | |
| 1.20.0 | 2 / 12 | |
| 1.19.3 | 2 / 12 | |
| 1.19.2 | 2 / 12 | |
| 1.19.1 | 2 / 12 | |
| 1.19.0 | 2 / 12 | |
| 1.18.1 | 2 / 12 | |
| 1.18.0 | 2 / 12 | |
| 1.17.0 | 2 / 12 | |
| 1.15.1 | 2 / 12 | |
| 1.14.0 | 2 / 12 | |
| 1.11.0 | 2 / 12 | |
| 1.9.0 | 2 / 12 | |
| 1.8.0 | 2 / 12 | |
| 1.6.0 | 2 / 12 | |
| 1.5.0 | 2 / 12 | |
| 1.3.0 | 2 / 12 | |
| 1.1.1 | 2 / 12 |
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (michaelmyers) than the most recent previously approved version (opendog) on 2021-03-16, but michaelmyers is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (michaelmyers) than the most recent previously approved version (opendog) on 2021-03-16, but michaelmyers is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (opendog) than the most recent previously approved version (michaelmyers) on 2021-03-04, but opendog is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.