@getflip/swirl-icons
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 0.92.0 | 0 / 3 | |
| 0.91.0 | 0 / 3 | |
| 0.90.0 | 0 / 3 | |
| 0.89.0 | 0 / 3 | |
| 0.88.0 | 0 / 3 | |
| 0.87.0 | 0 / 3 | |
| 0.86.0 | 0 / 3 | |
| 0.85.0 | 0 / 3 | |
| 0.84.0 | 0 / 3 | |
| 0.83.0 | 0 / 3 | |
| 0.82.0 | 0 / 3 | |
| 0.81.0 | 0 / 3 | |
| 0.80.0 | 0 / 3 | |
| 0.79.0 | 0 / 3 | |
| 0.78.0 | 0 / 3 | |
| 0.77.0 | 0 / 3 | |
| 0.76.0 | 0 / 3 | |
| 0.75.0 | 0 / 3 | |
| 0.74.1 | 0 / 3 | |
| 0.74.0 | 0 / 3 | |
| 0.73.0 | 0 / 3 | |
| 0.52.0 | 0 / 3 | |
| 0.51.0 | 0 / 3 | |
| 0.50.0 | 0 / 3 | |
| 0.49.0 | 0 / 3 | |
| 0.48.0 | 0 / 3 | |
| 0.47.0 | 0 / 3 | |
| 0.46.0 | 0 / 3 | |
| 0.45.0 | 0 / 3 | |
| 0.44.0 | 0 / 3 | |
| 0.43.0 | 0 / 3 | |
| 0.42.0 | 0 / 3 | |
| 0.41.0 | 0 / 3 | |
| 0.40.0 | 0 / 3 | |
| 0.39.0 | 0 / 3 | |
| 0.38.0 | 0 / 3 | |
| 0.37.0 | 0 / 3 | |
| 0.36.0 | 0 / 3 | |
| 0.35.0 | 0 / 3 | |
| 0.34.0 | 0 / 3 | |
| 0.33.0 | 0 / 3 | |
| 0.32.0 | 0 / 3 | |
| 0.31.0 | 0 / 3 | |
| 0.30.0 | 0 / 3 | |
| 0.29.0 | 0 / 3 | |
| 0.28.0 | 0 / 3 | |
| 0.27.0 | 0 / 3 | |
| 0.26.0 | 0 / 3 | |
| 0.25.0 | 0 / 3 | |
| 0.24.0 | 0 / 3 | |
| 0.23.0 | 0 / 3 |
v0.92.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.91.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (psiekmann) than the most recent previously approved version (getflipapp) on 2025-12-09, but psiekmann is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.