← Home

@vizzly/services

npm
16
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

jamesbowersbrandon.bellgt-rm-0306

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@vizzly/joi AI (dependencies): First-party scoped fork of joi within same org/monorepo. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are first-party scoped packages plus lodash, no malicious behavior. ai
npm-metadata no-description AI (npm-metadata): Stable pattern across this org's packages; not indicative of malice. ai
bogus-package bogus-package AI (bogus-package): Internal org package with 2072 versions; missing metadata is a consistent pattern, not a spam/malware indicator. ai

Versions (showing 16 of 16)

Version Deps Published
0.15.2 3 / 9
0.15.1 3 / 9
0.15.0 3 / 9
0.12.0 3 / 9
0.11.0 0 / 7
0.10.0 0 / 7
0.9.1 0 / 7
0.9.0 0 / 7
0.8.2 0 / 7
0.8.1 0 / 7
0.8.0 0 / 7
0.7.4 0 / 7
0.7.3 0 / 7
0.7.2 0 / 7
0.7.1 0 / 7
0.7.0 0 / 7

v0.12.0

1 finding
LOW No provenance attestation provenance

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

v0.11.0

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.1

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.2

1 finding
LOW No provenance attestation provenance

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

v0.8.1

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.4

1 finding
LOW No provenance attestation provenance

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

v0.7.3

1 finding
LOW No provenance attestation provenance

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

v0.7.2

1 finding
LOW No provenance attestation provenance

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

v0.7.1

1 finding
LOW No provenance attestation provenance

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

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