@dcl/memory-cache-component
In-memory cache component for core components library
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): Transition from decentralandbot to GitHub Actions CI publishing is consistent with Decentraland org automation; SLSA attestation confirms integrity. | ai | |
| phantom-deps | phantom-dep:@well-known-components/interfaces | AI (phantom-deps): Declared as a peer/type dependency and referenced in config; not a direct import by design. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 3 / 1 | |
| 2.3.0 | 3 / 1 | |
| 2.2.4 | 3 / 1 | |
| 2.2.3 | 3 / 1 | |
| 2.2.2 | 3 / 1 | |
| 2.2.1 | 3 / 1 | |
| 2.2.0 | 3 / 2 | |
| 2.1.0 | 3 / 2 | |
| 2.0.1 | 3 / 2 | |
| 2.0.0 | 3 / 2 |
v2.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. 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.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.