@toptal/picasso-skeleton-loader
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is benign given CI/CD publish flow for this established package. | ai | |
| provenance | publisher-changed | AI (provenance): Toptal org migrated publishing to GitHub Actions CI; SLSA attestation confirms legitimate repo-based build. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI migration; SLSA attestation and org context confirm legitimacy. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-utils | AI (dependencies): Internal sibling dep from the same Toptal/picasso monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@toptal/picasso-button | AI (dependencies): Internal sibling dep from the same Toptal/picasso monorepo; expected pattern across all versions. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.0.70 | 4 / 1 | |
| 1.0.69 | 4 / 1 | |
| 1.0.68 | 4 / 1 | |
| 1.0.67 | 4 / 1 | |
| 1.0.66 | 4 / 1 | |
| 1.0.65 | 4 / 1 | |
| 1.0.64 | 4 / 1 | |
| 1.0.63 | 4 / 1 | |
| 1.0.62 | 4 / 1 | |
| 1.0.61 | 4 / 1 | |
| 1.0.60 | 4 / 1 | |
| 1.0.59 | 4 / 1 | |
| 1.0.58 | 4 / 1 |
v1.0.70
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.68
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.67
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.63
2 findingsThis version was published by a different npm account than previous versions on 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.62
2 findingsThis version was published by a different npm account than previous versions on 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.61
2 findingsThis version was published by a different npm account than previous versions on 2025-09-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.60
2 findingsThis version was published by a different npm account than previous versions on 2025-09-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.