@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 21 of 21)
| 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 | |
| 2.7.0 | 0 / 7 | |
| 2.6.0 | 0 / 7 | |
| 2.5.2 | 0 / 7 | |
| 2.5.1 | 0 / 5 | |
| 2.5.0 | 0 / 5 | |
| 2.4.0 | 0 / 5 | |
| 2.3.0 | 0 / 5 | |
| 2.2.1 | 0 / 5 | |
| 2.2.0 | 0 / 5 | |
| 2.1.0 | 0 / 5 | |
| 2.0.0 | 0 / 5 |
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.