remotedev-serialize
Serialize unserializable data and parse it back.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): methuselah96 is a legitimate Redux DevTools maintainer; the transfer to the reduxjs org monorepo is documented and the publisher has a clean 330/0 track record. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by stable package being absorbed into the redux-devtools monorepo; no malicious indicators present. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.9 | 1 / 1 | |
| 0.1.8 | 1 / 3 | |
| 0.1.7 | 1 / 3 | |
| 0.1.6 | 1 / 3 | |
| 0.1.5 | 1 / 3 | |
| 0.1.4 | 1 / 3 | |
| 0.1.3 | 1 / 3 | |
| 0.1.2 | 1 / 3 | |
| 0.1.1 | 1 / 3 | |
| 0.1.0 | 1 / 3 |
v0.1.9
2 findingsThis version was published by a different npm account than previous versions on 2020-08-14. 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.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.