@ooneex/migrations
39
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
fkdiomande
Keywords
bundatabasemigrationsooneexschematypescriptversioning
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): @ooneex org pattern: sparse metadata is consistent across their published packages; not a spam/malware signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-wide pattern of minimal metadata; not indicative of malicious intent. | ai | |
| phantom-deps | phantom-dep:@ooneex/logger | AI (phantom-deps): Same-org dep; likely re-exported or used indirectly. Stable false positive for this package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 1 / 1 | |
| 1.6.1 | 2 / 1 | |
| 1.6.0 | 2 / 1 | |
| 1.5.2 | 2 / 1 | |
| 1.5.1 | 2 / 1 | |
| 1.5.0 | 2 / 1 | |
| 1.4.0 | 2 / 1 | |
| 1.3.7 | 2 / 1 | |
| 1.3.6 | 2 / 1 | |
| 1.3.5 | 2 / 1 | |
| 1.3.4 | 2 / 1 | |
| 1.3.3 | 2 / 1 | |
| 1.3.1 | 2 / 1 | |
| 1.3.0 | 2 / 1 | |
| 1.2.5 | 2 / 1 | |
| 1.2.4 | 2 / 1 | |
| 1.2.3 | 2 / 1 | |
| 1.2.2 | 2 / 1 | |
| 1.2.1 | 2 / 1 | |
| 1.2.0 | 2 / 1 | |
| 1.1.1 | 2 / 1 | |
| 1.1.0 | 2 / 1 | |
| 1.0.0 | 2 / 1 | |
| 0.17.0 | 2 / 1 | |
| 0.16.0 | 2 / 1 | |
| 0.15.0 | 2 / 1 | |
| 0.14.0 | 2 / 1 | |
| 0.13.0 | 2 / 1 | |
| 0.12.0 | 2 / 1 | |
| 0.11.0 | 2 / 1 | |
| 0.10.0 | 2 / 1 | |
| 0.9.0 | 2 / 1 | |
| 0.8.0 | 2 / 1 | |
| 0.7.0 | 2 / 1 | |
| 0.6.0 | 2 / 1 | |
| 0.5.0 | 2 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.3.0 | 2 / 1 | |
| 0.0.1 | 2 / 1 |
v1.6.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.