@xapp/audio-search-widget
Audio Search Widget
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:store | AI (dependencies): store is a well-known localStorage wrapper lib, benign dependency. | ai | |
| provenance | publisher-changed | AI (provenance): Switch to GitHub Actions CI publisher is an automation transition, not compromise. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with CI-managed publishing; no other malicious signal. | ai | |
| phantom-deps | phantom-dep:store | AI (phantom-deps): store is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xapp/stentor-chat-widget | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:stentor-guards | AI (phantom-deps): Declared runtime dep in org ecosystem; phantom-dep heuristic false positive. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.94.1 | 7 / 44 | |
| 1.94.0 | 7 / 44 | |
| 1.91.0 | 7 / 44 | |
| 1.90.0 | 7 / 44 | |
| 1.88.0 | 7 / 44 | |
| 1.87.2 | 7 / 44 | |
| 1.87.1 | 7 / 44 | |
| 1.87.0 | 7 / 44 | |
| 1.86.0 | 7 / 44 | |
| 1.85.1 | 7 / 44 | |
| 1.85.0 | 7 / 44 | |
| 1.84.1 | 7 / 44 | |
| 1.84.0 | 7 / 44 | |
| 1.83.1 | 7 / 44 | |
| 1.82.1 | 7 / 44 | |
| 1.81.5 | 7 / 44 | |
| 1.81.1 | 7 / 44 | |
| 1.81.0 | 7 / 44 | |
| 1.80.0 | 7 / 43 | |
| 1.62.0 | 5 / 43 | |
| 1.60.1 | 5 / 43 | |
| 1.60.0 | 5 / 43 |
v1.94.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-22. 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.87.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.1
1 findingPackage 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.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.1
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.