@dynamic-labs/sdk-api
API SDK for app.dynamic.xyz
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
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 is a documented CI/CD migration pattern for this active, long-lived package. | ai |
Versions (showing 100 of 1073)
| Version | Deps | Published |
|---|---|---|
| 0.0.894 | 0 / 0 | |
| 0.0.893 | 0 / 0 | |
| 0.0.892 | 0 / 0 | |
| 0.0.891 | 0 / 0 | |
| 0.0.890 | 0 / 0 | |
| 0.0.889 | 0 / 0 | |
| 0.0.888 | 0 / 0 | |
| 0.0.887 | 0 / 0 | |
| 0.0.886 | 0 / 0 | |
| 0.0.885 | 0 / 0 | |
| 0.0.884 | 0 / 0 | |
| 0.0.883 | 0 / 0 | |
| 0.0.882 | 0 / 0 | |
| 0.0.881 | 0 / 0 | |
| 0.0.880 | 0 / 0 | |
| 0.0.879 | 0 / 0 | |
| 0.0.878 | 0 / 0 | |
| 0.0.877 | 0 / 0 | |
| 0.0.876 | 0 / 0 | |
| 0.0.875 | 0 / 0 | |
| 0.0.874 | 0 / 0 | |
| 0.0.873 | 0 / 0 | |
| 0.0.872 | 0 / 0 | |
| 0.0.871 | 0 / 0 | |
| 0.0.870 | 0 / 0 | |
| 0.0.869 | 0 / 0 | |
| 0.0.868 | 0 / 0 | |
| 0.0.864 | 0 / 0 | |
| 0.0.863 | 0 / 0 | |
| 0.0.862 | 0 / 0 | |
| 0.0.861 | 0 / 0 | |
| 0.0.860 | 0 / 0 | |
| 0.0.859 | 0 / 0 | |
| 0.0.858 | 0 / 0 | |
| 0.0.857 | 0 / 0 | |
| 0.0.856 | 0 / 0 | |
| 0.0.855 | 0 / 0 | |
| 0.0.854 | 0 / 0 | |
| 0.0.853 | 0 / 0 | |
| 0.0.852 | 0 / 0 | |
| 0.0.851 | 0 / 0 | |
| 0.0.850 | 0 / 0 | |
| 0.0.849 | 0 / 0 | |
| 0.0.848 | 0 / 0 | |
| 0.0.847 | 0 / 0 | |
| 0.0.846 | 0 / 0 | |
| 0.0.845 | 0 / 0 | |
| 0.0.844 | 0 / 0 | |
| 0.0.843 | 0 / 0 | |
| 0.0.842 | 0 / 0 | |
| 0.0.841 | 0 / 0 | |
| 0.0.840 | 0 / 0 | |
| 0.0.839 | 0 / 0 | |
| 0.0.838 | 0 / 0 | |
| 0.0.837 | 0 / 0 | |
| 0.0.831 | 0 / 0 | |
| 0.0.830 | 0 / 0 | |
| 0.0.829 | 0 / 0 | |
| 0.0.828 | 0 / 0 | |
| 0.0.827 | 0 / 0 | |
| 0.0.826 | 0 / 0 | |
| 0.0.825 | 0 / 0 | |
| 0.0.824 | 0 / 0 | |
| 0.0.823 | 0 / 0 | |
| 0.0.822 | 0 / 0 | |
| 0.0.821 | 0 / 0 | |
| 0.0.820 | 0 / 0 | |
| 0.0.819 | 0 / 0 | |
| 0.0.818 | 0 / 0 | |
| 0.0.817 | 0 / 0 | |
| 0.0.816 | 0 / 0 | |
| 0.0.815 | 0 / 0 | |
| 0.0.814 | 0 / 0 | |
| 0.0.813 | 0 / 0 | |
| 0.0.812 | 0 / 0 | |
| 0.0.811 | 0 / 0 | |
| 0.0.810 | 0 / 0 | |
| 0.0.809 | 0 / 0 | |
| 0.0.808 | 0 / 0 | |
| 0.0.807 | 0 / 0 | |
| 0.0.806 | 0 / 0 | |
| 0.0.805 | 0 / 0 | |
| 0.0.804 | 0 / 0 | |
| 0.0.803 | 0 / 0 | |
| 0.0.802 | 0 / 0 | |
| 0.0.801 | 0 / 0 | |
| 0.0.800 | 0 / 0 | |
| 0.0.799 | 0 / 0 | |
| 0.0.798 | 0 / 0 | |
| 0.0.797 | 0 / 0 | |
| 0.0.796 | 0 / 0 | |
| 0.0.795 | 0 / 0 | |
| 0.0.794 | 0 / 0 | |
| 0.0.793 | 0 / 0 | |
| 0.0.792 | 0 / 0 | |
| 0.0.791 | 0 / 0 | |
| 0.0.790 | 0 / 0 | |
| 0.0.789 | 0 / 0 | |
| 0.0.788 | 0 / 0 | |
| 0.0.787 | 0 / 0 |
v0.0.894
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.893
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.892
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.891
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.890
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.889
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.888
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.887
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.886
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.885
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.884
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.883
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.882
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.881
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.880
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.879
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.878
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.877
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.876
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.875
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.874
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.873
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.872
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.871
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.870
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.869
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.868
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.864
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.863
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.862
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.861
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.860
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.859
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.858
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.857
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.856
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.855
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.854
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.