← Home

@forestadmin/datasource-mongoose

npm Repository Homepage
45
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pmerletforestbot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Monorepo team change, no behavioral signal alongside it. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with team reshuffle, not takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Long-lived low-traffic internal package; dormancy expected. ai

Versions (showing 45 of 45)

Version Deps Published
1.14.0 2 / 1
1.13.4 2 / 1
1.13.3 2 / 1
1.13.2 2 / 1
1.13.1 2 / 1
1.13.0 2 / 1
1.12.6 2 / 1
1.12.5 2 / 1
1.12.4 2 / 1
1.12.3 2 / 1
1.12.2 2 / 1
1.12.1 2 / 1
1.12.0 2 / 1
1.11.3 2 / 1
1.11.2 2 / 1
1.11.1 2 / 1
1.11.0 2 / 1
1.10.1 2 / 1
1.10.0 2 / 1
1.9.1 2 / 1
1.9.0 2 / 1
1.8.10 2 / 1
1.8.9 2 / 1
1.8.8 2 / 1
1.8.7 2 / 1
1.8.6 2 / 1
1.8.5 2 / 1
1.8.4 2 / 1
1.8.3 2 / 1
1.8.2 2 / 1
1.8.1 2 / 1
1.8.0 2 / 1
1.7.19 2 / 1
1.7.18 2 / 1
1.7.17 2 / 1
1.7.16 2 / 1
1.7.15 2 / 1
1.7.14 2 / 1
1.7.13 2 / 1
1.7.12 2 / 1
1.7.11 2 / 1
1.7.10 2 / 1
1.7.9 2 / 1
1.7.8 2 / 1
1.7.7 2 / 1

v1.14.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.12.2

2 findings
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-05-12, unremoved on npm for 432d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-05-12. It has since remained available on npm for 432 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-05-07, unremoved on npm for 437d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-05-07. It has since remained available on npm for 437 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.12.0

2 findings
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-04-15, unremoved on npm for 459d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-04-15. It has since remained available on npm for 459 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.3

2 findings
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-03-19, unremoved on npm for 486d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-03-19. It has since remained available on npm for 486 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.2

2 findings
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-03-11, unremoved on npm for 494d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-03-11. It has since remained available on npm for 494 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.1

2 findings
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-02-24, unremoved on npm for 509d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-02-24. It has since remained available on npm for 509 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.11.0

2 findings
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-02-21, unremoved on npm for 512d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-02-21. It has since remained available on npm for 512 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.10.1

2 findings
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-02-05, unremoved on npm for 528d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-02-05. It has since remained available on npm for 528 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-01-29, unremoved on npm for 535d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-01-29. It has since remained available on npm for 535 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.9.1

2 findings
MEDIUM Publisher changed: arnaudbesnier → forestbot (on 2025-01-28, unremoved on npm for 536d) provenance

This version was published by a different npm account (forestbot) than the most recent previously approved version (arnaudbesnier) on 2025-01-28. It has since remained available on npm for 536 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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.10

1 finding
LOW No provenance attestation provenance

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

v1.8.9

1 finding
LOW No provenance attestation provenance

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

v1.8.8

1 finding
LOW No provenance attestation provenance

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

v1.8.7

1 finding
LOW No provenance attestation provenance

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

v1.8.6

1 finding
LOW No provenance attestation provenance

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

v1.8.5

1 finding
LOW No provenance attestation provenance

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

v1.8.4

1 finding
LOW No provenance attestation provenance

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

v1.8.3

1 finding
LOW No provenance attestation provenance

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

v1.8.2

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

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.19

1 finding
LOW No provenance attestation provenance

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

v1.7.18

1 finding
LOW No provenance attestation provenance

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

v1.7.17

1 finding
LOW No provenance attestation provenance

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

v1.7.16

1 finding
LOW No provenance attestation provenance

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

v1.7.15

1 finding
LOW No provenance attestation provenance

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

v1.7.14

1 finding
LOW No provenance attestation provenance

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

v1.7.13

1 finding
LOW No provenance attestation provenance

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

v1.7.12

1 finding
LOW No provenance attestation provenance

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

v1.7.11

1 finding
LOW No provenance attestation provenance

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

v1.7.10

1 finding
LOW No provenance attestation provenance

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

v1.7.9

1 finding
LOW No provenance attestation provenance

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

v1.7.8

1 finding
LOW No provenance attestation provenance

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

v1.7.7

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.