@axinom/mosaic-id-link-be
Integration utilities from id-service for Axinom Mosaic services
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Axinom org package with 921 versions and 4 approved packages; diff shows only test script changes, consistent with routine maintenance. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is a peer/codegen dependency for this GraphQL integration package; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:graphql-tag | AI (phantom-deps): graphql-tag used in codegen config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@axinom/mosaic-core | AI (phantom-deps): Same-org dependency used indirectly; stable false positive for this Axinom package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.40.0 | 9 / 7 | |
| 0.39.0 | 8 / 7 | |
| 0.38.0 | 8 / 7 | |
| 0.37.0 | 8 / 7 | |
| 0.36.0 | 8 / 8 | |
| 0.35.0 | 8 / 8 | |
| 0.34.0 | 8 / 8 | |
| 0.33.0 | 8 / 8 | |
| 0.32.0 | 8 / 8 | |
| 0.31.7 | 8 / 8 | |
| 0.31.6 | 8 / 8 | |
| 0.31.5 | 8 / 8 | |
| 0.31.4 | 8 / 8 | |
| 0.31.3 | 8 / 8 | |
| 0.31.2 | 8 / 8 | |
| 0.31.1 | 8 / 8 | |
| 0.31.0 | 8 / 8 | |
| 0.30.0 | 8 / 8 | |
| 0.29.0 | 8 / 8 | |
| 0.28.0 | 8 / 8 | |
| 0.27.0 | 8 / 8 | |
| 0.26.0 | 8 / 8 | |
| 0.25.0 | 8 / 8 | |
| 0.24.0 | 8 / 8 | |
| 0.23.0 | 8 / 8 | |
| 0.22.0 | 8 / 8 | |
| 0.21.0 | 8 / 8 |
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.