← Home

@hms-dbmi/viv

npm Repository Homepage
6
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

ngehlenborgilanbassgoldmanztkeller-markjohn-conroynickakhmetovlchoy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA attestation; this is the expected automated release pattern for this org. ai
typosquat typosquat.levenshtein:vite AI (typosquat): Scoped @hms-dbmi/viv is a legitimate biomedical imaging library, not a typosquat of vite. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped @hms-dbmi/viv is a legitimate biomedical imaging library, not a typosquat of ajv. ai
phantom-deps phantom-dep:@vivjs/types AI (phantom-deps): @vivjs/types is a monorepo sibling used for type declarations; not imported at runtime by design. ai

Versions (showing 6 of 6)

Version Deps Published
0.21.0 7 / 0
0.20.1 7 / 0
0.20.0 7 / 0
0.19.0 7 / 0
0.18.2 7 / 0
0.18.0 7 / 0

v0.21.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.20.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.20.0

2 findings
HIGH Publisher changed: manzt → GitHub Actions (on 2026-03-24) provenance

This version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.19.0

2 findings
HIGH Publisher changed: manzt → GitHub Actions (on 2026-01-26) provenance

This version was published by a different npm account than previous versions on 2026-01-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.18.2

2 findings
HIGH Publisher changed: manzt → GitHub Actions (on 2026-01-09) provenance

This version was published by a different npm account than previous versions on 2026-01-09. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.18.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.