@stdlib/array-uint16 Apache-2.0 12 versions

@stdlib/array-uint16

npm Repository Homepage

Uint16Array.

12

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

stdlib-botkgryteplaneshifterrreusser

Keywords

stdlibstdtypestypesdatastructurearraytypedtyped arraytyped-arrayuint16arrayuint16uint16_tintegerintuintunsignedshort

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Common for older stdlib packages; not a malicious signal.	ai	2026/07/24
npm-metadata	url-dep:tape	AI (npm-metadata): Dev-only test dependency pinned to a known fork; not a runtime risk.	ai	2026/07/24
dependencies	unvetted-dep:@stdlib/assert-has-uint16array-support	AI (dependencies): Sibling stdlib package; consistent pattern across all @stdlib/* packages.	ai	2026/04/29

Versions (showing 12 of 12)

Version	Deps	Published
0.2.3	1 / 0	2026-02-08
0.2.2	1 / 0	2024-07-27
0.2.1	1 / 0	2024-02-22
0.2.0	1 / 17	2024-02-14
0.1.1	1 / 16	2023-10-09
0.1.0	1 / 16	2023-09-23
0.0.6	1 / 16	2022-02-16
0.0.5	1 / 16	2021-08-22
0.0.4	1 / 16	2021-07-07
0.0.3	1 / 16	2021-06-27
0.0.2	1 / 16	2021-06-16
0.0.1	1 / 16	2021-06-15

v0.2.2

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.