@stigg/api-client-js
This library was generated with [Nx](https://nx.dev).
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Org-level publisher rotation for an established SDK; new publisher has strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass removal consistent with org account consolidation, not a hostile takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 747 versions in registry; dormancy likely reflects a gap in this specific package's release cadence, not account takeover. | ai |
Versions (showing 40 of 141)
| Version | Deps | Published |
|---|---|---|
| 5.89.0 | 2 / 0 | |
| 5.87.1 | 2 / 0 | |
| 5.84.0 | 2 / 0 | |
| 5.82.0 | 2 / 0 | |
| 5.80.1 | 2 / 0 | |
| 5.77.0 | 2 / 0 | |
| 5.75.0 | 2 / 0 | |
| 5.74.0 | 2 / 0 | |
| 5.72.0 | 2 / 0 | |
| 5.71.0 | 2 / 0 | |
| 5.67.0 | 2 / 0 | |
| 5.66.0 | 2 / 0 | |
| 5.65.0 | 2 / 0 | |
| 5.64.0 | 2 / 0 | |
| 5.63.0 | 2 / 0 | |
| 5.62.0 | 2 / 0 | |
| 5.61.1 | 2 / 0 | |
| 5.57.7 | 2 / 0 | |
| 5.56.0 | 2 / 0 | |
| 5.53.0 | 2 / 0 | |
| 5.46.0 | 2 / 0 | |
| 5.45.0 | 2 / 0 | |
| 5.43.0 | 2 / 0 | |
| 5.39.0 | 2 / 0 | |
| 5.35.0 | 2 / 0 | |
| 5.32.0 | 2 / 0 | |
| 5.29.0 | 2 / 0 | |
| 5.28.0 | 2 / 0 | |
| 5.21.0 | 2 / 0 | |
| 5.18.0 | 2 / 0 | |
| 5.15.0 | 2 / 0 | |
| 5.14.0 | 2 / 0 | |
| 5.13.0 | 2 / 0 | |
| 5.12.0 | 2 / 0 | |
| 5.9.0 | 2 / 0 | |
| 5.1.0 | 2 / 0 | |
| 5.0.0 | 2 / 0 | |
| 4.7.0 | 2 / 0 | |
| 4.6.0 | 2 / 0 | |
| 4.5.0 | 2 / 0 |
v5.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.80.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.57.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.