@azure/search-documents
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
azure-sdkmicrosoft1esmicrosoft-oss-releases
Keywords
azurecloud
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Major version rewrite of established Microsoft Azure SDK; dormancy reflects development cycle, not account takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft-oss-releases is a known Microsoft OSS automation account; expected for Azure SDK packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @azure-rest/core-client is a first-party Microsoft Azure SDK package; expected dependency for v13 refactor. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version rewrite with multi-platform dist outputs (browser/esm/commonjs/react-native) explains the large file count increase. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit TypeScript runtime dependency; stable false positive for this package. | ai |
v13.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.