@norskvideo/norsk-sdk No license 51 versions

@norskvideo/norsk-sdk

npm

51

Versions

—

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

nwolversonadrianroesrstrongrobashton

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:grpc-es-bridge	AI (phantom-deps): New gRPC utility dep aligns with SDK's grpc-js usage; likely used via generated/bundled code.	ai	2026/07/27
semgrep	semgrep:shady-links-raw-ip	AI (semgrep): Localhost default URL fallback, not a remote exfiltration endpoint; stable pattern for this SDK.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Scoped SDK package with no description/repo is consistent across all 466 versions; not indicative of spam.	ai	2026/04/29

Versions (showing 51 of 61)

View all versions

Version	Deps	Published
1.0.402	6 / 9	2026-07-26
1.0.401	5 / 9	2025-04-15
1.0.400	5 / 9	2025-02-17
1.0.399	5 / 9	2025-01-28
1.0.398	5 / 9	2025-01-10
1.0.397	5 / 9	2024-12-12
1.0.396	5 / 9	2024-12-10
1.0.395	5 / 9	2024-12-02
1.0.392	5 / 7	2024-11-10
1.0.391	5 / 7	2024-11-03
1.0.390	5 / 7	2024-10-28
1.0.389	5 / 7	2024-10-28
1.0.388	5 / 7	2024-10-24
1.0.387	5 / 7	2024-10-20
1.0.386	5 / 7	2024-10-14
1.0.385	5 / 7	2024-09-27
1.0.384	5 / 7	2024-09-21
1.0.383	5 / 7	2024-09-19
1.0.382	5 / 7	2024-09-15
1.0.380	5 / 7	2024-09-11
1.0.379	5 / 7	2024-09-10
1.0.378	5 / 7	2024-09-10
1.0.377	5 / 7	2024-09-08
1.0.376	5 / 7	2024-09-05
1.0.375	5 / 7	2024-09-01
1.0.374	5 / 7	2024-08-30
1.0.373	5 / 7	2024-08-29
1.0.372	5 / 7	2024-08-20
1.0.370	5 / 7	2024-08-12
1.0.368	5 / 7	2024-07-26
1.0.367	5 / 7	2024-07-19
1.0.365	5 / 7	2024-06-19
1.0.364	5 / 7	2024-06-14
1.0.363	5 / 7	2024-06-05
1.0.360	5 / 7	2024-05-29
1.0.359	5 / 7	2024-05-16
1.0.358	5 / 4	2024-04-29
1.0.357	5 / 4	2024-04-12
1.0.356	5 / 4	2024-03-28
1.0.354	5 / 4	2024-03-18
1.0.352	4 / 3	2024-02-23
1.0.351	4 / 3	2024-02-22
1.0.350	4 / 3	2024-02-02
1.0.349	4 / 3	2024-01-19
1.0.348	4 / 3	2023-12-14
1.0.347	4 / 3	2023-12-13
1.0.346	4 / 3	2023-12-05
1.0.345	4 / 3	2023-11-27
1.0.344	4 / 3	2023-11-23
1.0.343	4 / 3	2023-11-07
1.0.342	4 / 3	2023-10-23

v1.0.402

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: robashton → adrianroe (on 2026-07-26, known maintainer) provenance

This version was published by a different npm account (adrianroe) than the most recent previously approved version (robashton) on 2026-07-26, but adrianroe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.400

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.399

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.398

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.397

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.396

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: adrianroe → robashton (on 2024-12-10, known maintainer) provenance

This version was published by a different npm account (robashton) than the most recent previously approved version (adrianroe) on 2024-12-10, but robashton is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.395

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: adrianroe → robashton (on 2024-12-02, known maintainer) provenance

This version was published by a different npm account (robashton) than the most recent previously approved version (adrianroe) on 2024-12-02, but robashton is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.392

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.391

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.390

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.389

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.388

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.387

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.386

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.385

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.384

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.383

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.382

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.380

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.379

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.378

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.377

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.376

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.375

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.374

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.373

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.372

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.370

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.368

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.367

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.365

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.364

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.363

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.360

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.359

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.

v1.0.358

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.

v1.0.357

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: adrianroe → nwolverson (on 2024-04-12, known maintainer) provenance

This version was published by a different npm account (nwolverson) than the most recent previously approved version (adrianroe) on 2024-04-12, but nwolverson is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.356

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.354

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.352

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.351

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.350

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.349

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.348

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.347

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.346

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.345

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.344

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: nwolverson → adrianroe (on 2023-11-23, known maintainer) provenance

This version was published by a different npm account (adrianroe) than the most recent previously approved version (nwolverson) on 2023-11-23, but adrianroe is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.343

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: adrianroe → nwolverson (on 2023-11-07, known maintainer) provenance

This version was published by a different npm account (nwolverson) than the most recent previously approved version (adrianroe) on 2023-11-07, but nwolverson is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.342

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.