@stdlib/math-base-special-round
Round a numeric value to the nearest integer.
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 test dependency pinned to a fork branch; not shipped in runtime code. | ai | |
| phantom-deps | phantom-dep:@stdlib/math-base-napi-unary | AI (phantom-deps): stdlib org dep used via native binding, not direct JS import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): stdlib build tooling dep; not directly imported in JS but used in build pipeline. | ai | |
| phantom-deps | phantom-dep:@stdlib/math-base-assert-is-nan | AI (phantom-deps): Same-org stdlib dep; phantom detection is a false positive for stdlib's architecture. | ai | |
| phantom-deps | phantom-dep:@stdlib/math-base-special-floor | AI (phantom-deps): Same-org stdlib dep; phantom detection is a false positive for stdlib's architecture. | ai | |
| phantom-deps | phantom-dep:@stdlib/math-base-assert-is-negative-zero | AI (phantom-deps): Same-org stdlib dep; phantom detection is a false positive for stdlib's architecture. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 5 / 0 | |
| 0.3.0 | 5 / 0 | |
| 0.2.1 | 0 / 0 | |
| 0.2.0 | 0 / 10 | |
| 0.1.1 | 0 / 9 | |
| 0.1.0 | 0 / 9 | |
| 0.0.7 | 0 / 9 | |
| 0.0.6 | 0 / 9 | |
| 0.0.5 | 0 / 9 | |
| 0.0.4 | 0 / 9 | |
| 0.0.3 | 0 / 9 | |
| 0.0.2 | 0 / 9 | |
| 0.0.1 | 0 / 9 |
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.