@algolia/monitoring
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package migrated to GitHub Actions CI/CD publishing with SLSA provenance attestation — a legitimate and encouraged supply chain improvement for the Algolia org. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation via Sigstore confirms CI/CD publishing integrity; stable positive signal for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by GitHub Actions migration with SLSA attestation and no material code changes is consistent with legitimate org-level workflow modernization, not takeover. | ai | |
| dependencies | unvetted-dep:@algolia/client-common | AI (dependencies): First-party Algolia dependency from the same monorepo, published in lockstep. Not a third-party or suspicious dependency. | ai | |
| dependencies | unvetted-dep:@algolia/requester-browser-xhr | AI (dependencies): First-party Algolia dependency from the same monorepo, published in lockstep. Not a third-party or suspicious dependency. | ai | |
| dependencies | unvetted-dep:@algolia/requester-fetch | AI (dependencies): First-party Algolia dependency from the same monorepo, published in lockstep. Not a third-party or suspicious dependency. | ai | |
| dependencies | unvetted-dep:@algolia/requester-node-http | AI (dependencies): First-party Algolia dependency from the same monorepo, published in lockstep. Not a third-party or suspicious dependency. | ai |
Versions (showing 51 of 96)
| Version | Deps | Published |
|---|---|---|
| 1.53.0 | 4 / 6 | |
| 1.52.1 | 4 / 6 | |
| 1.52.0 | 4 / 6 | |
| 1.51.0 | 4 / 6 | |
| 1.50.2 | 4 / 6 | |
| 1.50.1 | 4 / 6 | |
| 1.50.0 | 4 / 6 | |
| 1.49.2 | 4 / 6 | |
| 1.49.1 | 4 / 6 | |
| 1.49.0 | 4 / 6 | |
| 1.48.2 | 4 / 6 | |
| 1.48.1 | 4 / 6 | |
| 1.48.0 | 4 / 6 | |
| 1.47.0 | 4 / 6 | |
| 1.46.4 | 4 / 6 | |
| 1.46.3 | 4 / 6 | |
| 1.46.2 | 4 / 6 | |
| 1.46.1 | 4 / 6 | |
| 1.46.0 | 4 / 6 | |
| 1.45.0 | 4 / 6 | |
| 1.44.0 | 4 / 6 | |
| 1.43.0 | 4 / 6 | |
| 1.42.0 | 4 / 6 | |
| 1.41.0 | 4 / 6 | |
| 1.40.1 | 4 / 6 | |
| 1.40.0 | 4 / 6 | |
| 1.39.0 | 4 / 6 | |
| 1.38.0 | 4 / 6 | |
| 1.37.0 | 4 / 6 | |
| 1.36.0 | 4 / 6 | |
| 1.35.0 | 4 / 6 | |
| 1.34.1 | 4 / 6 | |
| 1.34.0 | 4 / 6 | |
| 1.33.0 | 4 / 6 | |
| 1.32.0 | 4 / 6 | |
| 1.31.0 | 4 / 6 | |
| 1.30.0 | 4 / 6 | |
| 1.29.0 | 4 / 6 | |
| 1.28.0 | 4 / 6 | |
| 1.27.0 | 4 / 6 | |
| 1.26.0 | 4 / 6 | |
| 1.25.0 | 4 / 6 | |
| 1.24.0 | 4 / 6 | |
| 1.23.4 | 4 / 6 | |
| 1.23.3 | 4 / 6 | |
| 1.23.2 | 4 / 6 | |
| 1.23.1 | 4 / 6 | |
| 1.23.0 | 4 / 6 | |
| 1.22.0 | 4 / 6 | |
| 1.21.0 | 4 / 6 | |
| 1.20.4 | 4 / 6 |
v1.53.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.52.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.49.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.49.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.49.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.48.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.48.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.48.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.47.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.46.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.46.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.46.2
2 findingsThis version was published by a different npm account than previous versions on 2025-12-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.46.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
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.22.0
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.