← Home

@firebase/firestore-types

npm Repository Homepage

@firebase/firestore Types

100
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

firebase-opsfeiyang.chengoogle-wombotchholland

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): google-wombot is Google's established Firebase automation publisher; transition from firebase-ops to google-wombot is a known, recurring pattern across Firebase packages. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (chholland, feiyang.chen, google-wombot) are recognized Firebase/Google team members and automation accounts. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers reflect normal team turnover at Google/Firebase; not indicative of a takeover given the legitimate new maintainers. ai
publish-pattern dormant-publish AI (publish-pattern): Types-only companion package; long dormancy is expected as it only needs updates when the public API changes significantly. ai
source-diff source-size-dropped AI (source-diff): Package ships only index.d.ts; size reduction reflects API simplification in a types declaration file, not malicious code replacement. ai

Versions (showing 100 of 274)

Hide prereleases
Version Deps Published
3.0.4 0 / 1
3.0.3 0 / 1
3.0.2 0 / 1
3.0.1 0 / 1
3.0.0 0 / 1
2.5.1 0 / 1
2.5.0 0 / 1
2.4.0 0 / 1
2.3.0 0 / 1
2.2.0 0 / 1
2.1.0 0 / 1
2.0.0 0 / 1
1.14.0 0 / 1
1.13.0 0 / 1
1.12.1 0 / 1
1.12.0 0 / 1
1.11.0 0 / 1
1.10.3 0 / 1
1.10.2 0 / 1
1.10.1 0 / 1
1.10.0 0 / 1
1.9.2 0 / 1
1.9.1 0 / 1
1.9.0 0 / 1
1.8.1 0 / 1
1.8.0 0 / 1
1.7.0 0 / 1
1.6.2 0 / 1
1.6.1 0 / 1
1.6.0 0 / 1
1.5.0 0 / 1
1.4.4 0 / 1
1.4.3 0 / 1
1.4.2 0 / 1
1.4.1 0 / 1
1.4.0 0 / 1
1.3.0 0 / 1
1.2.1 0 / 1
1.2.0 0 / 1
1.1.2 0 / 1
1.1.1 0 / 1
1.1.0 0 / 1
1.0.3 0 / 1
1.0.2 0 / 1
1.0.1 0 / 1
1.0.0 0 / 1
0.8.0 0 / 1
0.7.0 0 / 1
0.6.0 0 / 1
0.5.0 0 / 1
0.4.3 0 / 1
0.4.2 0 / 1
0.4.1 0 / 1
0.4.0 0 / 0
0.3.0 0 / 0
0.2.2 0 / 1
0.2.1 0 / 1
0.1.1 0 / 1
0.1.0 0 / 1
3.0.3-ssl-check.4f23f3343 0 / 1
3.0.3-firebase-studio-sdk-integration.fe1264c00 0 / 1
3.0.3-firebase-studio-sdk-integration.f7536090e 0 / 1
3.0.3-firebase-studio-sdk-integration.dd7924e1b 0 / 1
3.0.3-firebase-studio-sdk-integration.dbac496fa 0 / 1
3.0.3-firebase-studio-sdk-integration.d15eeea26 0 / 1
3.0.3-firebase-studio-sdk-integration.bffdabd70 0 / 1
3.0.3-firebase-studio-sdk-integration.a528caf5f 0 / 1
3.0.3-firebase-studio-sdk-integration.9de25069c 0 / 1
3.0.3-firebase-studio-sdk-integration.927daddb8 0 / 1
3.0.3-firebase-studio-sdk-integration.556d1bed2 0 / 1
3.0.3-firebase-studio-sdk-integration.33b86206f 0 / 1
3.0.3-firebase-studio-sdk-integration.226be0bb1 0 / 1
3.0.3-firebase-studio-sdk-integration.1adc0ae1f 0 / 1
3.0.3-firebase-studio-sdk-integration.12759bc2e 0 / 1
3.0.3-firebase-studio-sdk-integration.11d58925e 0 / 1
3.0.3-firebase-studio-sdk-integration.0d857eae1 0 / 1
3.0.3-firebase-studio-sdk-integration.0615f555a 0 / 1
3.0.3-eap-vertexai-hybridinference.e83974308 0 / 1
3.0.3-eap-vertexai-hybridinference.5fa83b371 0 / 1
3.0.3-eap-vertexai-hybridinference.43a69d5da 0 / 1
3.0.3-eap-vertexai-hybgoog.dc3794a2b 0 / 1
3.0.3-eap-vertexai-hybgoog.abf0491ae 0 / 1
3.0.3-eap-vertexai-hybgoog.31261ca31 0 / 1
3.0.3-eap-firestore-pipelines.2.e4cdd2e06 0 / 1
3.0.3-eap-firestore-pipelines.1.f9c4cdec7 0 / 1
3.0.3-eap-ai-hybridinference.c16cbf1a3 0 / 1
3.0.3-eap-ai-hybridinference.58d92df33 0 / 1
3.0.3-canary.f9aaeca46 0 / 1
3.0.3-canary.f9254b6d2 0 / 1
3.0.3-canary.f92069a21 0 / 1
3.0.3-canary.f8334eade 0 / 1
3.0.3-canary.f73e08b21 0 / 1
3.0.3-canary.f5fc6bf76 0 / 1
3.0.3-canary.f4e0086e3 0 / 1
3.0.3-canary.f2ecae7df 0 / 1
3.0.3-canary.f18b25f73 0 / 1
3.0.3-canary.f11b55294 0 / 1
3.0.3-canary.f0b0398eb 0 / 1
3.0.3-canary.f06cbf99b 0 / 1
3.0.3-canary.efc0117ae 0 / 1
Showing 100 of 274 Next page →

v3.0.4

1 finding
LOW No provenance attestation provenance

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

v1.14.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2020-10-15) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-10-15. This could indicate a legitimate maintainer transition or an account compromise.

v1.13.0

1 finding
LOW No provenance attestation provenance

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

v1.12.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2020-08-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-27. This could indicate a legitimate maintainer transition or an account compromise.

v1.12.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → chholland (on 2020-07-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-09. This could indicate a legitimate maintainer transition or an account compromise.

v1.11.0

1 finding
LOW No provenance attestation provenance

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

v1.10.3

1 finding
LOW No provenance attestation provenance

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

v1.10.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2020-05-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-21. This could indicate a legitimate maintainer transition or an account compromise.

v1.10.1

1 finding
LOW No provenance attestation provenance

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

v1.10.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2020-03-05) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-05. This could indicate a legitimate maintainer transition or an account compromise.

v1.9.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → feiyang.chen (on 2020-02-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-02-28. This could indicate a legitimate maintainer transition or an account compromise.

v1.9.1

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-12-06) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-12-06. This could indicate a legitimate maintainer transition or an account compromise.

v1.8.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-11-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-21. This could indicate a legitimate maintainer transition or an account compromise.

v1.7.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-11-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-07. This could indicate a legitimate maintainer transition or an account compromise.

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-10-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-10. This could indicate a legitimate maintainer transition or an account compromise.

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.4

1 finding
LOW No provenance attestation provenance

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

v1.4.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-07-19) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-07-19. This could indicate a legitimate maintainer transition or an account compromise.

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-06-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-13. This could indicate a legitimate maintainer transition or an account compromise.

v1.3.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → chholland (on 2019-05-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-05-07. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → feiyang.chen (on 2019-04-30) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-30. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: chholland → feiyang.chen (on 2019-04-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-18. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2019-04-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-11. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → feiyang.chen (on 2019-03-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-21. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → chholland (on 2019-03-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-14. This could indicate a legitimate maintainer transition or an account compromise.

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: feiyang.chen → chholland (on 2019-02-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-14. This could indicate a legitimate maintainer transition or an account compromise.

v1.0.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → feiyang.chen (on 2019-01-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-24. This could indicate a legitimate maintainer transition or an account compromise.

v1.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → feiyang.chen (on 2019-01-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-18. This could indicate a legitimate maintainer transition or an account compromise.

v0.8.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jshcrowthe → feiyang.chen (on 2018-12-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-12-07. This could indicate a legitimate maintainer transition or an account compromise.

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.2

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.

v0.2.1

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.

v0.1.1

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.

v0.1.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.

v3.0.3-ssl-check.4f23f3343

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.

v3.0.3-firebase-studio-sdk-integration.fe1264c00

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.

v3.0.3-firebase-studio-sdk-integration.f7536090e

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.

v3.0.3-firebase-studio-sdk-integration.dd7924e1b

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.

v3.0.3-firebase-studio-sdk-integration.dbac496fa

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.

v3.0.3-firebase-studio-sdk-integration.d15eeea26

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.

v3.0.3-firebase-studio-sdk-integration.bffdabd70

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.

v3.0.3-firebase-studio-sdk-integration.a528caf5f

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.

v3.0.3-firebase-studio-sdk-integration.9de25069c

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.

v3.0.3-firebase-studio-sdk-integration.927daddb8

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.

v3.0.3-firebase-studio-sdk-integration.556d1bed2

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.

v3.0.3-firebase-studio-sdk-integration.33b86206f

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.

v3.0.3-firebase-studio-sdk-integration.226be0bb1

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.

v3.0.3-firebase-studio-sdk-integration.1adc0ae1f

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.

v3.0.3-firebase-studio-sdk-integration.12759bc2e

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.

v3.0.3-firebase-studio-sdk-integration.11d58925e

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.

v3.0.3-firebase-studio-sdk-integration.0d857eae1

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.

v3.0.3-firebase-studio-sdk-integration.0615f555a

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.

v3.0.3-eap-vertexai-hybridinference.e83974308

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.

v3.0.3-eap-vertexai-hybridinference.5fa83b371

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.

v3.0.3-eap-vertexai-hybridinference.43a69d5da

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.

v3.0.3-eap-vertexai-hybgoog.dc3794a2b

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.

v3.0.3-eap-vertexai-hybgoog.abf0491ae

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.

v3.0.3-eap-vertexai-hybgoog.31261ca31

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.

v3.0.3-eap-firestore-pipelines.2.e4cdd2e06

1 finding
LOW No provenance attestation provenance

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

v3.0.3-eap-firestore-pipelines.1.f9c4cdec7

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.

v3.0.3-eap-ai-hybridinference.c16cbf1a3

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.

v3.0.3-eap-ai-hybridinference.58d92df33

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.

v3.0.3-canary.f9aaeca46

1 finding
LOW No provenance attestation provenance

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

v3.0.3-canary.f9254b6d2

1 finding
LOW No provenance attestation provenance

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

v3.0.3-canary.f92069a21

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.

v3.0.3-canary.f8334eade

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.

v3.0.3-canary.f73e08b21

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.

v3.0.3-canary.f5fc6bf76

1 finding
LOW No provenance attestation provenance

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

v3.0.3-canary.f4e0086e3

1 finding
LOW No provenance attestation provenance

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

v3.0.3-canary.f2ecae7df

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.

v3.0.3-canary.f18b25f73

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.

v3.0.3-canary.f11b55294

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.

v3.0.3-canary.f0b0398eb

1 finding
LOW No provenance attestation provenance

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

v3.0.3-canary.f06cbf99b

1 finding
LOW No provenance attestation provenance

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

v3.0.3-canary.efc0117ae

1 finding
LOW No provenance attestation provenance

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