← Home

@spences10/pi-team-mode

51
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

spences10

Keywords

agentorchestrationpipi-packageteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@spences10/pi-sqlite-core AI (dependencies): Same-author sibling package within the same monorepo, not a third-party dep. ai
publish-pattern new-deps-added AI (publish-pattern): Internal monorepo split, matches established publisher's normal pattern. ai
provenance no-provenance AI (provenance): Publisher has 110 approved packages; lack of provenance is consistent across their releases and not a risk indicator here. ai

Versions (showing 51 of 56)

View all versions
Version Deps Published
0.0.56 1 / 7
0.0.55 1 / 7
0.0.54 1 / 7
0.0.53 1 / 7
0.0.52 1 / 7
0.0.51 1 / 7
0.0.50 1 / 7
0.0.49 1 / 7
0.0.48 2 / 7
0.0.47 1 / 6
0.0.46 1 / 6
0.0.45 1 / 6
0.0.44 0 / 6
0.0.43 0 / 6
0.0.42 0 / 6
0.0.41 0 / 6
0.0.40 3 / 6
0.0.39 3 / 6
0.0.38 3 / 6
0.0.37 3 / 6
0.0.36 3 / 6
0.0.35 3 / 6
0.0.34 3 / 6
0.0.33 3 / 6
0.0.32 3 / 6
0.0.31 3 / 6
0.0.30 3 / 6
0.0.29 3 / 6
0.0.28 3 / 6
0.0.27 3 / 6
0.0.26 3 / 6
0.0.25 3 / 6
0.0.24 3 / 6
0.0.23 3 / 3
0.0.22 3 / 3
0.0.21 3 / 3
0.0.20 3 / 3
0.0.19 6 / 3
0.0.18 6 / 3
0.0.17 6 / 3
0.0.16 6 / 3
0.0.15 6 / 3
0.0.14 6 / 3
0.0.13 6 / 3
0.0.12 6 / 3
0.0.11 6 / 3
0.0.10 6 / 3
0.0.9 6 / 3
0.0.8 5 / 3
0.0.7 5 / 3
0.0.6 5 / 3

v0.0.56

1 finding
INFO No provenance attestation provenance

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

v0.0.55

1 finding
INFO No provenance attestation provenance

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

v0.0.54

1 finding
INFO No provenance attestation provenance

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

v0.0.53

1 finding
INFO No provenance attestation provenance

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

v0.0.52

1 finding
INFO No provenance attestation provenance

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

v0.0.51

1 finding
INFO No provenance attestation provenance

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

v0.0.50

1 finding
INFO No provenance attestation provenance

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

v0.0.49

1 finding
INFO No provenance attestation provenance

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

v0.0.48

1 finding
INFO No provenance attestation provenance

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

v0.0.47

1 finding
INFO No provenance attestation provenance

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

v0.0.46

1 finding
INFO No provenance attestation provenance

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

v0.0.45

1 finding
INFO No provenance attestation provenance

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

v0.0.44

1 finding
INFO No provenance attestation provenance

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

v0.0.43

1 finding
INFO No provenance attestation provenance

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

v0.0.42

1 finding
INFO No provenance attestation provenance

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

v0.0.41

1 finding
INFO No provenance attestation provenance

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

v0.0.40

1 finding
INFO No provenance attestation provenance

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

v0.0.39

1 finding
INFO No provenance attestation provenance

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

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

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

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

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

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