@stdlib/math-base-special-sin
Compute the sine of a 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 fork, no runtime/exfil impact; stable across stdlib packages. | ai | |
| phantom-deps | phantom-dep:@stdlib/math-base-napi-unary | AI (phantom-deps): stdlib native binding dep; declared for native addon support, not directly imported in JS layer. | ai | |
| phantom-deps | phantom-dep:@stdlib/utils-library-manifest | AI (phantom-deps): stdlib build tooling dep; declared for manifest support, not directly imported in JS layer. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 8 / 0 | |
| 0.3.0 | 8 / 0 | |
| 0.2.1 | 6 / 0 | |
| 0.2.0 | 6 / 13 | |
| 0.1.0 | 6 / 12 | |
| 0.0.6 | 4 / 12 | |
| 0.0.5 | 4 / 12 | |
| 0.0.4 | 4 / 12 | |
| 0.0.3 | 4 / 12 | |
| 0.0.2 | 4 / 12 | |
| 0.0.1 | 4 / 12 |
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.0
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.