@internetarchive/search-service
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 | publisher-changed | AI (provenance): jbuckner is an established IA publisher (32 approved, 0 rejected); transition appears legitimate. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 25 new source files consistent with feature expansion in a TypeScript library; no obfuscation or suspicious content indicated. | ai | |
| phantom-deps | phantom-dep:decorator-cache-getter | AI (phantom-deps): decorator-cache-getter is a declared runtime dep; phantom-dep fires because it's used indirectly via decorators, not a direct import. | ai | |
| provenance | no-provenance | AI (provenance): Established Internet Archive package with 211 versions; lack of provenance is consistent with its history and not a security concern for this org. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.7.2 | 3 / 23 | |
| 2.7.1 | 3 / 23 | |
| 2.7.0 | 3 / 23 | |
| 2.6.0 | 3 / 23 | |
| 2.5.3 | 3 / 23 | |
| 2.5.2 | 3 / 23 | |
| 2.5.1 | 3 / 23 | |
| 2.5.0 | 3 / 23 | |
| 2.4.1 | 3 / 23 | |
| 2.4.0 | 3 / 23 | |
| 2.3.2 | 3 / 23 | |
| 2.3.1 | 3 / 23 | |
| 2.3.0 | 3 / 23 | |
| 2.2.1 | 4 / 23 | |
| 2.1.0 | 4 / 23 |
v2.7.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dualcnhq) than the most recent previously approved version (nsharma123) on 2026-06-05, but dualcnhq 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.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.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.
v2.6.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
2 findingsThis version was published by a different npm account than previous versions on 2025-09-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
2 findingsThis version was published by a different npm account than previous versions on 2025-09-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
2 findingsThis version was published by a different npm account than previous versions on 2025-09-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.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.
v2.2.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.
v2.1.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.