@xyo-network/archivist-model-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
Versions (showing 51 of 103)
| Version | Deps | Published |
|---|---|---|
| 7.2.1 | 2 / 11 | |
| 7.2.0 | 2 / 13 | |
| 7.1.1 | 2 / 13 | |
| 7.1.0 | 2 / 13 | |
| 7.0.11 | 2 / 25 | |
| 7.0.10 | 1 / 27 | |
| 7.0.9 | 2 / 26 | |
| 7.0.8 | 2 / 28 | |
| 7.0.7 | 2 / 26 | |
| 7.0.6 | 2 / 26 | |
| 7.0.5 | 2 / 26 | |
| 7.0.4 | 2 / 26 | |
| 7.0.3 | 2 / 26 | |
| 7.0.2 | 2 / 26 | |
| 7.0.1 | 2 / 26 | |
| 7.0.0 | 2 / 26 | |
| 6.1.0 | 2 / 26 | |
| 6.0.4 | 2 / 28 | |
| 6.0.3 | 2 / 29 | |
| 6.0.2 | 2 / 29 | |
| 6.0.1 | 2 / 33 | |
| 6.0.0 | 2 / 21 | |
| 5.6.4 | 2 / 21 | |
| 5.5.6 | 2 / 21 | |
| 5.5.5 | 2 / 21 | |
| 5.5.4 | 2 / 21 | |
| 5.5.3 | 2 / 22 | |
| 5.5.2 | 2 / 22 | |
| 5.5.1 | 2 / 22 | |
| 5.5.0 | 2 / 22 | |
| 5.4.1 | 3 / 12 | |
| 5.4.0 | 3 / 12 | |
| 5.3.30 | 3 / 14 | |
| 5.3.22 | 3 / 19 | |
| 5.3.17 | 3 / 7 | |
| 5.3.16 | 3 / 7 | |
| 5.3.15 | 3 / 7 | |
| 5.3.14 | 3 / 7 | |
| 5.3.13 | 3 / 7 | |
| 5.3.12 | 3 / 7 | |
| 5.3.11 | 3 / 7 | |
| 5.3.10 | 3 / 7 | |
| 5.3.9 | 3 / 7 | |
| 5.3.8 | 3 / 7 | |
| 5.3.7 | 3 / 7 | |
| 5.3.6 | 3 / 6 | |
| 5.3.5 | 4 / 5 | |
| 5.3.4 | 4 / 5 | |
| 5.3.3 | 4 / 4 | |
| 5.3.2 | 4 / 4 | |
| 5.3.1 | 4 / 4 |
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
2 findingsPackage 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 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.