@stdlib/os-float-word-order
Platform float word order.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:tape | AI (npm-metadata): Dev-only tape fork pin, common across stdlib packages, no runtime risk. | ai | |
| phantom-deps | phantom-dep:@stdlib/cli | AI (phantom-deps): Same-org stdlib dependency, used indirectly by CLI tooling. | ai | |
| phantom-deps | phantom-dep:@stdlib/fs-read-file | AI (phantom-deps): Same-org stdlib dependency, heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): Same-org stdlib dependency, heuristic false positive. | ai | |
| provenance | no-provenance | AI (provenance): stdlib packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 1 / 0 | |
| 0.2.2 | 1 / 0 | |
| 0.2.1 | 1 / 0 | |
| 0.2.0 | 1 / 4 | |
| 0.1.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 | |
| 0.0.7 | 4 / 7 | |
| 0.0.6 | 4 / 7 | |
| 0.0.5 | 4 / 7 | |
| 0.0.4 | 4 / 7 | |
| 0.0.3 | 4 / 7 | |
| 0.0.2 | 4 / 7 | |
| 0.0.1 | 4 / 7 |
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.