@dynamic-labs/sdk-api-core
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 publisher reflects CI/CD automation; consistent across subsequent versions of this package. | ai |
Versions (showing 100 of 672)
| Version | Deps | Published |
|---|---|---|
| 0.0.681 | 0 / 0 | |
| 0.0.680 | 0 / 0 | |
| 0.0.679 | 0 / 0 | |
| 0.0.678 | 0 / 0 | |
| 0.0.677 | 0 / 0 | |
| 0.0.676 | 0 / 0 | |
| 0.0.675 | 0 / 0 | |
| 0.0.674 | 0 / 0 | |
| 0.0.673 | 0 / 0 | |
| 0.0.672 | 0 / 0 | |
| 0.0.671 | 0 / 0 | |
| 0.0.670 | 0 / 0 | |
| 0.0.669 | 0 / 0 | |
| 0.0.668 | 0 / 0 | |
| 0.0.667 | 0 / 0 | |
| 0.0.666 | 0 / 0 | |
| 0.0.665 | 0 / 0 | |
| 0.0.664 | 0 / 0 | |
| 0.0.663 | 0 / 0 | |
| 0.0.662 | 0 / 0 | |
| 0.0.661 | 0 / 0 | |
| 0.0.660 | 0 / 0 | |
| 0.0.659 | 0 / 0 | |
| 0.0.658 | 0 / 0 | |
| 0.0.657 | 0 / 0 | |
| 0.0.656 | 0 / 0 | |
| 0.0.655 | 0 / 0 | |
| 0.0.654 | 0 / 0 | |
| 0.0.653 | 0 / 0 | |
| 0.0.652 | 0 / 0 | |
| 0.0.651 | 0 / 0 | |
| 0.0.650 | 0 / 0 | |
| 0.0.649 | 0 / 0 | |
| 0.0.648 | 0 / 0 | |
| 0.0.647 | 0 / 0 | |
| 0.0.646 | 0 / 0 | |
| 0.0.645 | 0 / 0 | |
| 0.0.644 | 0 / 0 | |
| 0.0.643 | 0 / 0 | |
| 0.0.642 | 0 / 0 | |
| 0.0.641 | 0 / 0 | |
| 0.0.640 | 0 / 0 | |
| 0.0.639 | 0 / 0 | |
| 0.0.638 | 0 / 0 | |
| 0.0.637 | 0 / 0 | |
| 0.0.636 | 0 / 0 | |
| 0.0.635 | 0 / 0 | |
| 0.0.634 | 0 / 0 | |
| 0.0.633 | 0 / 0 | |
| 0.0.632 | 0 / 0 | |
| 0.0.631 | 0 / 0 | |
| 0.0.630 | 0 / 0 | |
| 0.0.629 | 0 / 0 | |
| 0.0.628 | 0 / 0 | |
| 0.0.627 | 0 / 0 | |
| 0.0.626 | 0 / 0 | |
| 0.0.625 | 0 / 0 | |
| 0.0.624 | 0 / 0 | |
| 0.0.623 | 0 / 0 | |
| 0.0.622 | 0 / 0 | |
| 0.0.621 | 0 / 0 | |
| 0.0.620 | 0 / 0 | |
| 0.0.619 | 0 / 0 | |
| 0.0.618 | 0 / 0 | |
| 0.0.617 | 0 / 0 | |
| 0.0.616 | 0 / 0 | |
| 0.0.615 | 0 / 0 | |
| 0.0.614 | 0 / 0 | |
| 0.0.613 | 0 / 0 | |
| 0.0.612 | 0 / 0 | |
| 0.0.611 | 0 / 0 | |
| 0.0.610 | 0 / 0 | |
| 0.0.609 | 0 / 0 | |
| 0.0.608 | 0 / 0 | |
| 0.0.607 | 0 / 0 | |
| 0.0.606 | 0 / 0 | |
| 0.0.605 | 0 / 0 | |
| 0.0.604 | 0 / 0 | |
| 0.0.603 | 0 / 0 | |
| 0.0.602 | 0 / 0 | |
| 0.0.601 | 0 / 0 | |
| 0.0.600 | 0 / 0 | |
| 0.0.599 | 0 / 0 | |
| 0.0.598 | 0 / 0 | |
| 0.0.597 | 0 / 0 | |
| 0.0.596 | 0 / 0 | |
| 0.0.595 | 0 / 0 | |
| 0.0.594 | 0 / 0 | |
| 0.0.593 | 0 / 0 | |
| 0.0.592 | 0 / 0 | |
| 0.0.591 | 0 / 0 | |
| 0.0.590 | 0 / 0 | |
| 0.0.589 | 0 / 0 | |
| 0.0.588 | 0 / 0 | |
| 0.0.587 | 0 / 0 | |
| 0.0.586 | 0 / 0 | |
| 0.0.585 | 0 / 0 | |
| 0.0.584 | 0 / 0 | |
| 0.0.583 | 0 / 0 | |
| 0.0.582 | 0 / 0 |
v0.0.659
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.658
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.657
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.656
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.655
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.654
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.653
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.652
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.651
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.650
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.649
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.648
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.647
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.646
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.645
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.644
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.643
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.642
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.641
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.640
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.639
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.638
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.637
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.636
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.635
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.634
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.633
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.632
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.631
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.630
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.629
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.628
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.627
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.626
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.625
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.624
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.623
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.622
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.621
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.620
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.619
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.618
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.617
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.616
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.615
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.614
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.613
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.612
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.611
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.610
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.609
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.608
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.607
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.606
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.605
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.604
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.603
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.602
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.601
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.600
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.599
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.598
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.597
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.596
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.595
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.594
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.593
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.592
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.591
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.590
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.589
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.588
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.587
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.586
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.585
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.584
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.583
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.582
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.