metro-cache MIT 36 versions

metro-cache

npm Repository Homepage

🚇 Cache layers for Metro.

36

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

fbmetro-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed-stale	AI (provenance): Historic publisher change by trusted cpojer, no takeover behavior.	ai	2026/07/21
maintainer-change	maintainer-takeover	AI (maintainer-change): Long-standing official Meta package; no takeover behavior, just stale maintainer metadata.	ai	2026/07/21
phantom-deps	phantom-dep:jest-serializer	AI (phantom-deps): jest-serializer used as jest snapshot serializer, referenced via config, not direct import.	ai	2026/07/21
semgrep	semgrep:eval-usage	AI (semgrep): eval builds an empty named class in test code; no external input, stable FP.	ai	2026/07/21
phantom-deps	phantom-dep:flow-enums-runtime	AI (phantom-deps): flow-enums-runtime is a standard Meta/Flow ecosystem dep declared for consumers of Flow types; not being directly imported in source is expected and stable for this package.	ai	2026/04/21

Versions (showing 36 of 136)

Version	Deps	Published
0.48.0	4 / 1	2018-10-05
0.47.1	4 / 1	2018-10-04
0.47.0	4 / 1	2018-09-27
0.46.0	4 / 1	2018-09-24
0.45.6	4 / 1	2018-09-21
0.45.5	4 / 1	2018-09-20
0.45.4	4 / 1	2018-09-19
0.45.3	4 / 1	2018-09-14
0.45.2	4 / 1	2018-09-12
0.45.1	4 / 1	2018-09-06
0.45.0	4 / 1	2018-08-30
0.44.0	4 / 1	2018-08-28
0.43.6	4 / 1	2018-08-16
0.43.5	4 / 1	2018-08-10
0.43.4	4 / 1	2018-08-03
0.43.3	4 / 1	2018-08-02
0.43.2	4 / 1	2018-08-01
0.43.1	4 / 1	2018-07-30
0.43.0	4 / 1	2018-07-27
0.42.2	4 / 1	2018-07-20
0.42.1	4 / 1	2018-07-10
0.40.1	4 / 1	2018-06-28
0.39.1	4 / 1	2018-06-14
0.38.3	4 / 1	2018-07-13
0.38.2	4 / 1	2018-07-11
0.38.0	4 / 1	2018-06-01
0.37.2	4 / 1	2018-06-01
0.37.1	4 / 1	2018-05-21
0.36.1	4 / 1	2018-04-27
0.31.0	3 / 0	2018-03-21
0.30.2	2 / 0	2018-03-16
0.30.1	2 / 0	2018-03-14
0.30.0	2 / 0	2018-03-10
0.29.0	2 / 0	2018-03-07
0.28.0	2 / 0	2018-02-26
0.27.0	0 / 0	2018-02-24

v0.48.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.47.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.47.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.46.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.45.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.45.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.45.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.45.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.45.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.45.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.45.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.44.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.43.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.42.2

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.42.1

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.40.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.39.1

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.38.3

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.38.2

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.38.0

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.37.2

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.37.1

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.36.1

2 findings

HIGH eval-usage: src.real/__tests__/Cache-test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.31.0

2 findings

HIGH eval-usage: src.real/__tests__/Cache.test.js:21 semgrep

eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. 19 | function createStore(name = '') { 20 | // eslint-disable-next-line no-eval > 21 | const TempClass = eval(`(class ${name} {})`); 22 | 23 | return Object.assign(new TempClass(), {

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.