@contrail/flexplm
Library used for integration with flexplm.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Same-org publisher with long clean track record; likely internal team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with internal team rotation, no behavior change accompanies it. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is same-scope first-party @contrail package, not third-party. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI upload command; child_process use is expected for a FlexPLM integration CLI tool. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-supplied mapping config file at runtime; standard plugin/config-loader pattern for this CLI. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @contrail-namespace library; sparse metadata is consistent with a private/org package, not spam. | ai |
Versions (showing 51 of 94)
| Version | Deps | Published |
|---|---|---|
| 1.7.2 | 6 / 7 | |
| 1.7.1 | 6 / 7 | |
| 1.7.0 | 6 / 7 | |
| 1.6.1 | 6 / 7 | |
| 1.6.0 | 6 / 7 | |
| 1.5.0 | 6 / 7 | |
| 1.4.0 | 6 / 7 | |
| 1.3.2 | 6 / 7 | |
| 1.3.1 | 6 / 7 | |
| 1.3.0 | 6 / 7 | |
| 1.2.1 | 6 / 7 | |
| 1.2.0 | 6 / 7 | |
| 1.1.66 | 6 / 7 | |
| 1.1.65 | 7 / 7 | |
| 1.1.64 | 6 / 7 | |
| 1.1.63 | 6 / 7 | |
| 1.1.62 | 6 / 7 | |
| 1.1.61 | 6 / 7 | |
| 1.1.60 | 6 / 7 | |
| 1.1.59 | 5 / 7 | |
| 1.1.58 | 5 / 7 | |
| 1.1.57 | 5 / 7 | |
| 1.1.56 | 5 / 7 | |
| 1.1.55 | 5 / 7 | |
| 1.1.54 | 5 / 7 | |
| 1.1.53 | 5 / 7 | |
| 1.1.52 | 5 / 7 | |
| 1.1.51 | 5 / 7 | |
| 1.1.50 | 5 / 7 | |
| 1.1.49 | 5 / 7 | |
| 1.1.48 | 5 / 7 | |
| 1.1.47 | 5 / 7 | |
| 1.1.46 | 5 / 7 | |
| 1.1.45 | 5 / 7 | |
| 1.1.44 | 5 / 7 | |
| 1.1.43 | 5 / 7 | |
| 1.1.42 | 5 / 7 | |
| 1.1.41 | 5 / 7 | |
| 1.1.40 | 5 / 7 | |
| 1.1.39 | 5 / 7 | |
| 1.1.37 | 5 / 7 | |
| 1.1.36 | 5 / 7 | |
| 1.1.35 | 5 / 7 | |
| 1.1.34 | 5 / 7 | |
| 1.1.33 | 5 / 7 | |
| 1.1.32 | 5 / 7 | |
| 1.1.31 | 5 / 7 | |
| 1.1.30 | 5 / 7 | |
| 1.1.29 | 5 / 7 | |
| 1.1.28 | 5 / 7 | |
| 1.1.27 | 5 / 7 |
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.