@getflip/swirl-tokens
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 | publisher-changed | AI (provenance): Package is published via GitHub Actions CI/CD with SLSA provenance; publisher=GitHub Actions is expected for this org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with transition to automated CI/CD publishing under the getflip org; no malicious indicators. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.14.3 | 0 / 7 | |
| 2.14.2 | 0 / 7 | |
| 2.14.1 | 0 / 7 | |
| 2.14.0 | 0 / 7 | |
| 2.13.0 | 0 / 7 | |
| 2.12.0 | 0 / 7 | |
| 2.11.0 | 0 / 7 | |
| 2.10.0 | 0 / 7 | |
| 2.9.0 | 0 / 7 | |
| 2.8.0 | 0 / 7 |
v2.14.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. 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.
v2.14.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-07. 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.
v2.14.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.