@synnaxlabs/client
The Synnax Client Library
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; expected for this monorepo going forward. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Active monorepo with 81 versions; large file additions are consistent with normal feature growth. | ai | |
| license | uncommon-license:BUSL-1.1 | AI (license): BUSL-1.1 is the established license for this package across all versions. | ai |
Versions (showing 82 of 82)
| Version | Deps | Published |
|---|---|---|
| 0.56.2 | 5 / 10 | |
| 0.56.1 | 5 / 10 | |
| 0.56.0 | 5 / 10 | |
| 0.55.0 | 4 / 10 | |
| 0.54.2 | 4 / 10 | |
| 0.54.1 | 4 / 10 | |
| 0.54.0 | 4 / 10 | |
| 0.53.1 | 4 / 10 | |
| 0.53.0 | 4 / 10 | |
| 0.52.3 | 4 / 10 | |
| 0.50.0 | 4 / 10 | |
| 0.49.3 | 4 / 10 | |
| 0.49.2 | 4 / 10 | |
| 0.49.0 | 4 / 10 | |
| 0.48.0 | 4 / 10 | |
| 0.47.0 | 4 / 10 | |
| 0.46.1 | 4 / 10 | |
| 0.46.0 | 4 / 10 | |
| 0.45.1 | 4 / 10 | |
| 0.45.0 | 4 / 10 | |
| 0.44.4 | 4 / 10 | |
| 0.44.3 | 4 / 10 | |
| 0.44.2 | 4 / 10 | |
| 0.44.1 | 4 / 10 | |
| 0.43.1 | 4 / 9 | |
| 0.43.0 | 4 / 9 | |
| 0.42.3 | 5 / 10 | |
| 0.42.1 | 5 / 10 | |
| 0.42.0 | 5 / 10 | |
| 0.41.0 | 5 / 10 | |
| 0.40.0 | 5 / 10 | |
| 0.39.0 | 5 / 10 | |
| 0.38.1 | 5 / 9 | |
| 0.38.0 | 5 / 9 | |
| 0.37.0 | 5 / 10 | |
| 0.36.0 | 4 / 11 | |
| 0.35.0 | 4 / 11 | |
| 0.34.0 | 4 / 11 | |
| 0.33.0 | 4 / 11 | |
| 0.32.0 | 4 / 9 | |
| 0.31.1 | 4 / 9 | |
| 0.31.0 | 4 / 9 | |
| 0.30.0 | 4 / 9 | |
| 0.29.0 | 4 / 9 | |
| 0.28.0 | 4 / 9 | |
| 0.27.0 | 4 / 9 | |
| 0.26.7 | 4 / 9 | |
| 0.26.1 | 4 / 9 | |
| 0.26.0 | 4 / 9 | |
| 0.25.0 | 4 / 9 | |
| 0.24.0 | 5 / 9 | |
| 0.23.1 | 5 / 9 | |
| 0.23.0 | 5 / 9 | |
| 0.22.1 | 5 / 9 | |
| 0.22.0 | 5 / 9 | |
| 0.21.0 | 4 / 9 | |
| 0.20.0 | 4 / 9 | |
| 0.19.0 | 4 / 9 | |
| 0.18.3 | 4 / 9 | |
| 0.18.2 | 4 / 9 | |
| 0.18.1 | 4 / 9 | |
| 0.18.0 | 4 / 9 | |
| 0.17.6 | 4 / 9 | |
| 0.17.5 | 4 / 9 | |
| 0.17.4 | 4 / 9 | |
| 0.17.3 | 4 / 8 | |
| 0.17.2 | 4 / 8 | |
| 0.17.1 | 4 / 8 | |
| 0.17.0 | 4 / 8 | |
| 0.16.4 | 4 / 8 | |
| 0.16.3 | 4 / 8 | |
| 0.15.3 | 4 / 8 | |
| 0.15.2 | 3 / 8 | |
| 0.15.1 | 3 / 8 | |
| 0.15.0 | 3 / 8 | |
| 0.14.0 | 3 / 8 | |
| 0.13.6 | 3 / 8 | |
| 0.13.5 | 3 / 8 | |
| 0.2.1 | 2 / 22 | |
| 0.1.3 | 2 / 22 | |
| 0.1.2 | 2 / 22 | |
| 0.1.1 | 2 / 22 |
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.