@egjs/react-flicking
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known maintainer manual publish; no behavioral change vs prior approved version. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived NAVER package; inactivity gap explained by build tooling migration, publisher is a known maintainer. | ai | |
| phantom-deps | phantom-dep:@cfcs/core | AI (phantom-deps): @cfcs/core is a declared runtime dep used transitively; stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.16.5 | 5 / 22 | |
| 4.16.4 | 5 / 22 | |
| 4.16.3 | 5 / 22 | |
| 4.16.2 | 5 / 22 | |
| 4.16.1 | 5 / 22 | |
| 4.16.0 | 5 / 22 | |
| 4.15.0 | 5 / 22 | |
| 4.14.4 | 5 / 22 | |
| 4.14.3 | 5 / 22 | |
| 4.14.2 | 5 / 22 | |
| 4.14.1 | 5 / 22 | |
| 4.14.0 | 5 / 22 | |
| 4.13.0 | 3 / 19 | |
| 4.12.0 | 3 / 19 | |
| 4.11.4 | 3 / 19 | |
| 4.11.3 | 3 / 19 |
v4.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: cjw783.
v4.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.3
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 (younkue) than the most recent previously approved version (braixen) on 2025-10-02, but younkue 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.
v4.14.2
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 (braixen) than the most recent previously approved version (cjw783) on 2025-09-22, but braixen 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.
v4.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.