← Home

@oclif/plugin-command-snapshot

generates and compares OCLIF plugins snapshot files

51
Versions
MIT
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

jimjagsalesforce-releases

Keywords

oclif-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package from trusted publisher; provenance absence is ecosystem-wide norm. ai
dependencies unvetted-dep:ts-json-schema-generator AI (dependencies): ts-json-schema-generator is a well-known TypeScript schema tool; its use here for schema generation is expected and benign. ai

Versions (showing 51 of 94)

View all versions
Version Deps Published
5.3.32 9 / 28
5.3.31 9 / 28
5.3.30 9 / 28
5.3.29 9 / 28
5.3.28 9 / 28
5.3.27 9 / 28
5.3.26 9 / 28
5.3.25 9 / 28
5.3.24 9 / 28
5.3.23 9 / 28
5.3.22 9 / 28
5.3.21 9 / 28
5.3.20 9 / 28
5.3.19 9 / 28
5.3.18 9 / 28
5.3.17 9 / 28
5.3.16 9 / 28
5.3.15 9 / 28
5.3.14 9 / 28
5.3.13 9 / 28
5.3.12 9 / 28
5.3.11 9 / 28
5.3.10 9 / 28
5.3.9 9 / 28
5.3.8 9 / 28
5.3.7 9 / 28
5.3.6 9 / 28
5.3.5 9 / 28
5.3.4 9 / 28
5.3.3 9 / 28
5.3.2 9 / 28
5.3.1 9 / 28
5.3.0 9 / 28
5.2.40 9 / 28
5.2.39 9 / 28
5.2.38 9 / 28
5.2.37 9 / 28
5.2.36 9 / 28
5.2.35 9 / 28
5.2.34 9 / 28
5.2.33 9 / 28
5.2.32 9 / 28
5.2.31 9 / 28
5.2.30 9 / 28
5.2.29 9 / 28
5.2.28 9 / 28
5.2.27 9 / 28
5.2.26 9 / 28
5.2.25 9 / 28
5.2.24 9 / 28
5.2.23 9 / 28

v5.3.32

1 finding
INFO No provenance attestation provenance

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

v5.3.31

1 finding
INFO No provenance attestation provenance

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

v5.3.30

1 finding
INFO No provenance attestation provenance

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

v5.3.29

1 finding
INFO No provenance attestation provenance

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

v5.2.38

1 finding
INFO No provenance attestation provenance

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

v5.2.37

1 finding
INFO No provenance attestation provenance

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

v5.2.36

1 finding
INFO No provenance attestation provenance

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

v5.2.35

1 finding
INFO No provenance attestation provenance

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

v5.2.34

1 finding
INFO No provenance attestation provenance

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

v5.2.33

1 finding
INFO No provenance attestation provenance

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

v5.2.32

1 finding
INFO No provenance attestation provenance

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

v5.2.31

1 finding
INFO No provenance attestation provenance

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

v5.2.30

1 finding
INFO No provenance attestation provenance

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

v5.2.29

1 finding
INFO No provenance attestation provenance

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

v5.2.28

1 finding
INFO No provenance attestation provenance

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

v5.2.27

1 finding
INFO No provenance attestation provenance

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

v5.2.26

1 finding
INFO No provenance attestation provenance

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

v5.2.25

1 finding
INFO No provenance attestation provenance

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

v5.2.24

1 finding
INFO No provenance attestation provenance

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

v5.2.23

1 finding
INFO No provenance attestation provenance

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