@xyo-network/module-abstract-mongodb
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jonesmac is an established publisher with 2562 approved packages; likely a legitimate org maintainer transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher xyo has 2185 approved packages; dormancy likely reflects monorepo release cadence, not account takeover. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance not used across the XYO Network package family. | ai |
Versions (showing 51 of 108)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 3 / 14 | |
| 7.2.0 | 3 / 16 | |
| 7.1.1 | 3 / 16 | |
| 7.1.0 | 3 / 16 | |
| 7.0.11 | 3 / 28 | |
| 7.0.10 | 3 / 29 | |
| 7.0.9 | 3 / 28 | |
| 7.0.8 | 3 / 30 | |
| 7.0.7 | 3 / 28 | |
| 7.0.6 | 3 / 28 | |
| 7.0.5 | 3 / 28 | |
| 7.0.4 | 3 / 28 | |
| 7.0.3 | 3 / 28 | |
| 7.0.2 | 3 / 28 | |
| 7.0.1 | 3 / 28 | |
| 7.0.0 | 3 / 28 | |
| 6.1.0 | 3 / 28 | |
| 6.0.4 | 3 / 30 | |
| 6.0.3 | 3 / 31 | |
| 6.0.2 | 3 / 31 | |
| 6.0.1 | 3 / 35 | |
| 6.0.0 | 3 / 29 | |
| 5.6.4 | 3 / 29 | |
| 5.6.3 | 3 / 29 | |
| 5.6.2 | 3 / 28 | |
| 5.6.1 | 3 / 28 | |
| 5.6.0 | 3 / 28 | |
| 5.5.6 | 3 / 28 | |
| 5.5.5 | 3 / 28 | |
| 5.5.4 | 3 / 28 | |
| 5.5.3 | 3 / 31 | |
| 5.5.2 | 1 / 33 | |
| 5.5.1 | 1 / 33 | |
| 5.5.0 | 1 / 33 | |
| 5.4.1 | 1 / 18 | |
| 5.4.0 | 1 / 18 | |
| 5.3.30 | 1 / 20 | |
| 5.3.26 | 3 / 17 | |
| 5.3.22 | 3 / 20 | |
| 5.3.20 | 6 / 11 | |
| 5.3.17 | 3 / 10 | |
| 5.3.16 | 3 / 10 | |
| 5.3.15 | 1 / 10 | |
| 5.3.13 | 1 / 10 | |
| 5.3.12 | 1 / 10 | |
| 5.3.11 | 1 / 10 | |
| 5.3.10 | 1 / 10 | |
| 5.3.8 | 1 / 10 | |
| 5.3.7 | 1 / 10 | |
| 5.3.6 | 1 / 9 | |
| 5.3.5 | 1 / 9 |
v7.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (joelbcarter) on 2026-07-15, but atrouw is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joelbcarter) than the most recent previously approved version (atrouw) on 2026-07-13, but joelbcarter is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.