@stdlib/math-base-assert-is-even
Test if a finite numeric value is an even number.
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, common stdlib pattern, no runtime impact. | ai | |
| provenance | no-provenance | AI (provenance): Common for older stdlib releases; not a malicious indicator. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-argv-double | AI (phantom-deps): Same N-API manifest pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-argv | AI (phantom-deps): N-API deps used via native binding manifest, not direct JS import; stable pattern for @stdlib packages. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): Library manifest utility used at build/native level, not directly imported in JS; stable FP. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-create-int32 | AI (phantom-deps): Same N-API manifest pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@stdlib/napi-export | AI (phantom-deps): Same N-API manifest pattern; not a phantom dep concern for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.2.5 | 6 / 0 | |
| 0.2.4 | 6 / 0 | |
| 0.2.3 | 2 / 0 | |
| 0.2.2 | 2 / 0 | |
| 0.2.1 | 1 / 0 | |
| 0.2.0 | 1 / 10 | |
| 0.1.0 | 1 / 9 | |
| 0.0.7 | 1 / 9 | |
| 0.0.6 | 1 / 9 | |
| 0.0.5 | 1 / 9 | |
| 0.0.4 | 1 / 9 | |
| 0.0.3 | 1 / 9 | |
| 0.0.2 | 1 / 9 | |
| 0.0.1 | 1 / 9 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.