@wisemen/nestjs-typeorm
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal org package; missing description is cosmetic, not a malice indicator here. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; low-risk internal library. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD with SLSA attestation; expected for this org's workflow. | ai | |
| provenance | missing-githead | AI (provenance): Consistent with GitHub Actions publish environment; SLSA attestation provides stronger commit linkage. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 0 / 7 | |
| 1.2.1 | 0 / 7 | |
| 1.2.0 | 0 / 7 | |
| 1.1.2 | 0 / 7 | |
| 1.1.1 | 0 / 7 | |
| 1.1.0 | 0 / 7 | |
| 1.0.2 | 0 / 7 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 | |
| 0.2.1 | 0 / 5 | |
| 0.2.0 | 0 / 5 | |
| 0.1.4 | 0 / 4 | |
| 0.1.3 | 0 / 4 | |
| 0.1.2 | 0 / 4 | |
| 0.1.1 | 0 / 4 | |
| 0.1.0 | 0 / 4 | |
| 0.0.37 | 0 / 4 | |
| 0.0.36 | 0 / 4 | |
| 0.0.35 | 0 / 4 | |
| 0.0.34 | 0 / 4 | |
| 0.0.33 | 0 / 4 | |
| 0.0.32 | 0 / 4 | |
| 0.0.31 | 0 / 4 | |
| 0.0.30 | 0 / 4 | |
| 0.0.29 | 0 / 4 | |
| 0.0.28 | 0 / 4 | |
| 0.0.27 | 0 / 4 | |
| 0.0.26 | 0 / 3 | |
| 0.0.25 | 0 / 3 | |
| 0.0.24 | 0 / 3 | |
| 0.0.23 | 2 / 3 | |
| 0.0.22 | 2 / 3 | |
| 0.0.21 | 4 / 3 | |
| 0.0.20 | 4 / 4 | |
| 0.0.19 | 4 / 4 | |
| 0.0.18 | 4 / 4 | |
| 0.0.17 | 4 / 4 | |
| 0.0.16 | 4 / 4 | |
| 0.0.15 | 4 / 4 | |
| 0.0.14 | 4 / 4 | |
| 0.0.13 | 4 / 4 | |
| 0.0.12 | 4 / 3 | |
| 0.0.11 | 4 / 3 | |
| 0.0.10 | 4 / 3 | |
| 0.0.9 | 4 / 3 | |
| 0.0.8 | 4 / 3 | |
| 0.0.7 | 4 / 3 | |
| 0.0.6 | 3 / 3 | |
| 0.0.5 | 3 / 3 | |
| 0.0.4 | 3 / 2 | |
| 0.0.3 | 2 / 2 | |
| 0.0.2 | 1 / 2 | |
| 0.0.1 | 4 / 2 |
v1.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
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 (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-04-17, but kobe-kwanten-wisemen 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.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
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 (jorenvandeweyer) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-04-11, but jorenvandeweyer 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.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
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 (kobe-kwanten-wisemen) than the most recent previously approved version (maartensijmkens) on 2025-04-06, but kobe-kwanten-wisemen 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.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
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 (maartensijmkens) than the most recent previously approved version (jorenvandeweyer) on 2025-03-06, but maartensijmkens 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.
v0.0.9
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 (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-03-04, but kobe-kwanten-wisemen 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.
v0.0.8
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 (jorenvandeweyer) than the most recent previously approved version (kobe-kwanten-wisemen) on 2025-02-26, but jorenvandeweyer 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.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
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 (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-02-13, but kobe-kwanten-wisemen 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.
v0.0.5
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 (kobe-kwanten-wisemen) than the most recent previously approved version (jorenvandeweyer) on 2025-02-12, but kobe-kwanten-wisemen 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.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.