← Home

deep-dot

3
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

vweevers

Keywords

getnesteddeepproperty

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance; repo ownership unchanged under vweevers org. ai
publish-pattern new-deps-added AI (publish-pattern): module-error is a well-known utility by the same original author (vweevers); not a suspicious addition. ai
source-diff source-size-tripled AI (source-diff): Size increase consistent with added TypeScript type declarations and new dependency, not injected payload. ai

Versions (showing 3 of 3)

Version Deps Published
1.1.0 1 / 6
1.0.0 1 / 6
0.0.2 0 / 0

v1.1.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.

v1.0.0

2 findings
HIGH Publisher changed: vweevers → GitHub Actions (on 2025-12-06) provenance

This version was published by a different npm account than previous versions on 2025-12-06. 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.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.