← Home

@toptal/picasso-quote

12
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

talbot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence is cosmetic given CI/CD publish with Sigstore attestation. ai
provenance no-provenance AI (provenance): Toptal Picasso monorepo consistently publishes without Sigstore provenance; stable false positive for this package family. ai
dependencies unvetted-dep:@toptal/picasso-container AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. ai
dependencies unvetted-dep:@toptal/picasso-typography AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. ai

Versions (showing 12 of 12)

Version Deps Published
2.0.11 2 / 1
2.0.10 2 / 1
2.0.9 2 / 1
2.0.8 2 / 1
2.0.7 2 / 1
2.0.6 2 / 1
2.0.5 2 / 1
2.0.4 2 / 1
2.0.3 2 / 1
2.0.2 2 / 1
2.0.1 2 / 1
2.0.0 2 / 1

v2.0.6

1 finding
INFO No provenance attestation provenance

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

v2.0.5

1 finding
INFO No provenance attestation provenance

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

v2.0.4

1 finding
INFO No provenance attestation provenance

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

v2.0.3

1 finding
INFO No provenance attestation provenance

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

v2.0.2

1 finding
INFO No provenance attestation provenance

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.