@transferwise/components
Neptune React components
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established org package; no provenance is a process gap, not a security signal for this publisher. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known polyfill runtime dep; not directly imported but legitimately used via babel transform. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped babel runtime; loaded by convention via babel plugin, not direct import. | ai | |
| phantom-deps | phantom-dep:@transferwise/neptune-tokens | AI (phantom-deps): Same-org design token package; likely consumed via CSS/Less rather than direct JS import. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 46.148.1 | 17 / 55 | |
| 46.148.0 | 17 / 55 | |
| 46.147.0 | 17 / 55 | |
| 46.146.0 | 17 / 55 | |
| 46.145.0 | 17 / 55 | |
| 46.144.1 | 17 / 55 | |
| 46.144.0 | 17 / 56 | |
| 46.143.1 | 17 / 56 | |
| 46.143.0 | 17 / 56 | |
| 46.142.0 | 17 / 56 | |
| 46.141.0 | 17 / 56 | |
| 46.140.1 | 17 / 56 | |
| 46.140.0 | 17 / 56 | |
| 46.139.0 | 17 / 56 | |
| 46.138.0 | 17 / 56 | |
| 46.137.1 | 17 / 56 | |
| 46.137.0 | 17 / 52 | |
| 46.136.1 | 17 / 52 | |
| 46.136.0 | 17 / 52 | |
| 46.135.3 | 17 / 52 | |
| 46.135.2 | 17 / 52 | |
| 46.135.1 | 19 / 52 | |
| 46.135.0 | 19 / 52 | |
| 46.134.0 | 19 / 52 |
v46.148.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.148.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.147.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.146.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.145.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.144.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.144.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.143.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.143.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.142.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.141.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.140.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.140.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.139.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.138.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.137.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.136.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v46.135.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v46.135.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v46.135.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v46.135.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v46.134.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.