@orion-js/migrations
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@orion-js/helpers | AI (phantom-deps): Same-org monorepo sibling; indirect usage pattern is stable across versions. | ai | |
| phantom-deps | phantom-dep:@orion-js/typed-model | AI (phantom-deps): Same-org monorepo sibling; indirect usage pattern is stable across versions. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 4 / 6 | |
| 4.3.5 | 4 / 6 | |
| 4.3.4 | 4 / 6 | |
| 4.3.3 | 4 / 6 | |
| 4.3.2 | 4 / 6 | |
| 4.3.1 | 4 / 6 | |
| 4.3.0 | 4 / 5 | |
| 4.2.10 | 4 / 6 | |
| 4.2.9 | 4 / 6 | |
| 4.2.8 | 4 / 6 | |
| 4.2.7 | 4 / 6 | |
| 4.2.6 | 4 / 6 | |
| 4.2.5 | 4 / 6 | |
| 4.2.4 | 4 / 6 | |
| 4.2.3 | 4 / 6 | |
| 4.2.1 | 4 / 6 | |
| 4.2.0 | 4 / 6 | |
| 4.1.12 | 4 / 6 | |
| 4.1.10 | 4 / 6 | |
| 4.1.9 | 4 / 6 | |
| 4.1.8 | 4 / 6 | |
| 4.1.7 | 4 / 6 | |
| 4.1.6 | 4 / 6 | |
| 4.1.5 | 4 / 6 | |
| 4.1.4 | 4 / 6 | |
| 4.1.3 | 4 / 6 | |
| 4.1.2 | 4 / 6 | |
| 4.1.1 | 4 / 6 | |
| 4.1.0 | 4 / 6 | |
| 4.0.34 | 4 / 6 | |
| 4.0.33 | 4 / 6 | |
| 4.0.32 | 4 / 6 | |
| 4.0.31 | 5 / 6 | |
| 4.0.30 | 5 / 6 | |
| 4.0.29 | 5 / 6 | |
| 4.0.28 | 5 / 6 | |
| 4.0.27 | 5 / 6 | |
| 4.0.26 | 5 / 6 | |
| 4.0.25 | 5 / 6 | |
| 4.0.24 | 5 / 6 | |
| 4.0.23 | 5 / 6 | |
| 4.0.22 | 5 / 6 |
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.