@dynamic-labs/assert-package-version
Utility to assert package versions
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 is a documented CI/CD migration pattern for this established org; stable going forward. | ai |
Versions (showing 88 of 288)
| Version | Deps | Published |
|---|---|---|
| 4.20.6 | 1 / 0 | |
| 4.20.5 | 1 / 0 | |
| 4.20.4 | 1 / 0 | |
| 4.20.3 | 1 / 0 | |
| 4.20.2 | 1 / 0 | |
| 4.20.1 | 1 / 0 | |
| 4.20.0 | 1 / 0 | |
| 4.19.7 | 1 / 0 | |
| 4.19.6 | 1 / 0 | |
| 4.19.5 | 1 / 0 | |
| 4.19.4 | 1 / 0 | |
| 4.19.3 | 1 / 0 | |
| 4.19.2 | 1 / 0 | |
| 4.19.1 | 1 / 0 | |
| 4.19.0 | 1 / 0 | |
| 4.18.8 | 1 / 0 | |
| 4.18.7 | 1 / 0 | |
| 4.18.6 | 1 / 0 | |
| 4.18.5 | 1 / 0 | |
| 4.18.4 | 1 / 0 | |
| 4.18.3 | 1 / 0 | |
| 4.18.2 | 1 / 0 | |
| 4.18.1 | 1 / 0 | |
| 4.18.0 | 1 / 0 | |
| 4.17.0 | 1 / 0 | |
| 4.16.0 | 1 / 0 | |
| 4.15.0 | 1 / 0 | |
| 4.14.0 | 1 / 0 | |
| 4.13.0 | 1 / 0 | |
| 4.12.4 | 1 / 0 | |
| 4.12.3 | 1 / 0 | |
| 4.12.2 | 1 / 0 | |
| 4.12.1 | 1 / 0 | |
| 4.12.0 | 1 / 0 | |
| 4.11.2 | 1 / 0 | |
| 4.11.1 | 1 / 0 | |
| 4.11.0 | 1 / 0 | |
| 4.10.4 | 1 / 0 | |
| 4.10.3 | 1 / 0 | |
| 4.10.2 | 1 / 0 | |
| 4.10.1 | 1 / 0 | |
| 4.10.0 | 1 / 0 | |
| 4.9.12 | 1 / 0 | |
| 4.9.11 | 1 / 0 | |
| 4.9.10 | 1 / 0 | |
| 4.9.9 | 1 / 0 | |
| 4.9.8 | 1 / 0 | |
| 4.9.7 | 1 / 0 | |
| 4.9.6 | 1 / 0 | |
| 4.9.5 | 1 / 0 | |
| 4.9.4 | 1 / 0 | |
| 4.9.3 | 1 / 0 | |
| 4.9.2 | 1 / 0 | |
| 4.9.1 | 1 / 0 | |
| 4.9.0 | 1 / 0 | |
| 4.8.6 | 1 / 0 | |
| 4.8.5 | 1 / 0 | |
| 4.8.4 | 1 / 0 | |
| 4.8.3 | 1 / 0 | |
| 4.8.2 | 1 / 0 | |
| 4.8.1 | 1 / 0 | |
| 4.8.0 | 1 / 0 | |
| 4.7.2 | 1 / 0 | |
| 4.7.1 | 1 / 0 | |
| 4.7.0 | 1 / 0 | |
| 4.6.3 | 1 / 0 | |
| 4.6.2 | 1 / 0 | |
| 4.6.1 | 1 / 0 | |
| 4.6.0 | 1 / 0 | |
| 4.5.3 | 1 / 0 | |
| 4.5.2 | 1 / 0 | |
| 4.5.1 | 1 / 0 | |
| 4.5.0 | 1 / 0 | |
| 4.4.4 | 1 / 0 | |
| 4.4.3 | 1 / 0 | |
| 4.4.2 | 1 / 0 | |
| 4.4.1 | 1 / 0 | |
| 4.4.0 | 1 / 0 | |
| 4.3.2 | 1 / 0 | |
| 4.3.1 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.3 | 1 / 0 | |
| 4.2.2 | 1 / 0 | |
| 4.2.1 | 1 / 0 | |
| 4.2.0 | 1 / 0 | |
| 4.1.0 | 1 / 0 | |
| 4.0.1 | 1 / 0 | |
| 4.0.0 | 1 / 0 |
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
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.
v4.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.