@cloudtower/eagle
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-copy-to-clipboard | AI (phantom-deps): Declared dependency; used indirectly via build config. Stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-copy-to-clipboard is a well-established, safe utility package; not a suspicious addition. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed legitimate by SLSA provenance attestation on this and subsequent versions. | ai | |
| dependencies | unvetted-dep:react-highlight-words | AI (dependencies): Popular React text highlighting library, no risk indicators. | ai | |
| dependencies | unvetted-dep:antd5 | AI (dependencies): antd5 is an alias for [email protected], a major well-known React UI library. | ai | |
| dependencies | unvetted-dep:@cloudtower/rc-notification | AI (dependencies): First-party sibling package from the same cloudtower org. | ai | |
| dependencies | unvetted-dep:@cloudtower/icons-react | AI (dependencies): First-party sibling package from the same cloudtower org. | ai | |
| dependencies | unvetted-dep:timezones.json | AI (dependencies): timezones.json is a stable, widely-used timezone data package. | ai | |
| dependencies | unvetted-dep:react-svg-unique-id | AI (dependencies): Small, well-known React utility package with no risk indicators. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 4100.0.7 | 23 / 69 | |
| 4100.0.3 | 23 / 69 | |
| 4100.0.2 | 19 / 67 | |
| 4100.0.1 | 19 / 67 | |
| 4100.0.0 | 19 / 67 | |
| 490.0.15 | 19 / 67 | |
| 490.0.13 | 19 / 67 | |
| 490.0.12 | 19 / 67 | |
| 490.0.5 | 19 / 67 | |
| 490.0.4 | 19 / 67 | |
| 490.0.3 | 19 / 67 | |
| 490.0.2 | 19 / 67 | |
| 481.0.3 | 18 / 66 | |
| 481.0.2 | 18 / 66 | |
| 0.35.9 | 19 / 67 | |
| 0.35.8 | 19 / 67 | |
| 0.35.7 | 19 / 67 | |
| 0.35.5 | 18 / 66 | |
| 0.35.3 | 18 / 66 | |
| 0.34.31 | 18 / 66 | |
| 0.34.29 | 18 / 66 | |
| 0.34.28 | 18 / 66 | |
| 0.34.24 | 18 / 66 | |
| 0.34.22 | 18 / 66 | |
| 0.34.21 | 18 / 66 | |
| 0.34.20 | 18 / 66 | |
| 0.34.19 | 18 / 66 | |
| 0.34.18 | 18 / 66 | |
| 0.34.17 | 18 / 66 |
v4100.0.7
2 findingsThis version was published by a different npm account than previous versions on 2026-04-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.
v4100.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4100.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-24. This could indicate a legitimate maintainer transition or an account compromise.
v4100.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.
v490.0.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.
v490.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
v490.0.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
v490.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v490.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v490.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v490.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v481.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.